Abstract

A development system providing methodology for improving system performance by decreasing recompilation of dependent source modules is described. During operation, the system keeps track of several pieces of information. From the outset, the system has kept track of the timestamps of sources (e.g., A.java file in a Java system) and compiled files thereof (e.g., A.class class file in a Java system). Examination of the timestamps leads to detection of those files which have been modified. The system will recompile A.java in the following circumstances: (1) A.class is not found, (2) A.java has a different timestamp, or (3) A.class has a different timestamp. Otherwise, the system does not invoke a recompile. If a recompilation in not required, the system then looks to the imports for determining whether the imports are consistent. Here, the system checks the timestamps of imports, possibly recompiling one or more of the modules providing the imports. If the imports have been recompiled, then the system must check the root module for determining whether it remains consistent with the imports--that is, whether A is still consistent with its imports. If not, the system recompiles the source file (e.g., A.java).

Other References

• Interprocedural Optimization: Eliminating Unnecessary Recompilation by Burke et al published in ACM, 1994
• Separate Compilation for Standard ML by Appel et al published in ACM, 1994
• Smart Recompilation and the GNAT Compiler by Gasperoni et al published ACM, 1994
• Crelier, Regis, Separate Compilation and Module Extension, Dissertation submitted to the Swiss Federal Institute of Technology Zurich, 1994. (Complete bound copy submitted