| B. Cmelik, "Concurrent Make: The Design and Implementation of a Distributed Program in Concurrent C," in Concurrent C Project, AT&T Bell Laboratories, Murray - Hill, NJ, 1986. |
....overhead because an extra process is introduced for each virtual processor to control the execution of the command block. It is not possible to solve problem [4] in a transparent way, since pmake cannot deduce which commands may not run in parallel in the same directory. Concurrent make, or cmake [18], provides a facility to specify which command blocks should execute mutually exclusively, i.e. only one command block in a certain group of command blocks may run at a time. To do so, one has to define a mutex on the group of command blocks, by declaring a rule having target name .MUTEX, with ....
....the commands have finished. Nmake does not provide an explicit facility to prevent certain commands from being executed mutually exclusively. It is possible, however, to run the critical commands in the foreground shell, thus imposing sequential execution. 7.2. Concurrent Make Concurrent Make [18], or cmake, was developed primarily to reduce the time needed to run a make process, not to increase make s functionality. It is written in Concurrent C [20] and is based on the Version 8 UNIX make. The latter requires the user to indicate explicitly which commands can execute in parallel, ....
B. Cmelik, "Concurrent Make: The Design and Implementation of a Distributed Program in Concurrent C," in Concurrent C Project, AT&T Bell Laboratories, Murray - Hill, NJ, 1986.
No context found.
B. Cmelik, "Concurrent Make: The Design and Implementation of a Distributed Program in Concurrent C," in Concurrent C Project, AT&T Bell Laboratories, Murray Hill, NJ, 1986.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC