Browse Prior Art Database

Dual Process Synchronous Control Compilation Procedure

IP.com Disclosure Number: IPCOM000114761D
Original Publication Date: 1995-Jan-01
Included in the Prior Art Database: 2005-Mar-29
Document File: 2 page(s) / 81K

Publishing Venue

IBM

Related People

Jensen, B: AUTHOR [+4]

Abstract

Disclosed is a process to accelerate the compilation of a set of source programs by using multiple processing threads. This process is known as the Dual Process Synchronous Control Compilation procedure (DPSCC).

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Dual Process Synchronous Control Compilation Procedure

      Disclosed is a process to accelerate the compilation of a set
of source programs by using multiple processing threads.  This
process is known as the Dual Process Synchronous Control Compilation
procedure (DPSCC).

      After the development of a product and initial testing are
complete, the entire product is recompiled and prepared for final
testing.  This recompile requires numerous source modules to be
compiled which can take a significant amount of time.  In order to
reduce recompile time, DPSCC was developed.  The DPSCC methodology
decreases recompile time by separating the compiler procedure from
the disk write procedure.  This dual path operation significantly
increases the throughput of source compiles.

      DPSCC is composed of four parts: the main program, the compiler
executable, a background daemon, and a shared memory segment through
which the compiler and background daemon communicate.  When DPSCC is
called through a command line function, the user specifies a file
that contains a list of source programs to be compiled.  This list,
the source name list, is passed to the main program which first gets
control.  The main program loads and starts a background daemon which
will write the compiled object code to disk.  The main program then
creates the shared memory segment "/DPSCC/OBJ" through which the
compiler module will pass object code to the background daemon and
creates a semaphore named "/DPSCC/WRITE".  Next, the compiler module
is called and passed the name of the source name list file.  The
compiler accesses each of the source files named in the list and
performs the compile.  As each source module is compiled, the object
code is placed into the shared memory segment along with the name of
the source module.  When the object module is loaded into the shared
memory segment or the shared memory segment is filled, the compiler
sets the "/DPSCC/WRITE" semaphore to indicate that the daemon is to
sta...