The C++ programming language
Integral-C—a practical environment for C programming
SDE 2 Proceedings of the second ACM SIGSOFT/SIGPLAN software engineering symposium on Practical software development environments
A Macroscopic Profile of Program Compilation and Linking
IEEE Transactions on Software Engineering
DAC '84 Proceedings of the 21st Design Automation Conference
SLIPE '85 Proceedings of the ACM SIGPLAN 85 symposium on Language issues in programming environments
Linking programs incrementally
Linking programs incrementally
An overview of a dynamic programming environment based on extensibility
Nordic Journal of Computing
WIESS'00 Proceedings of the 1st conference on Industrial Experiences with Systems Software - Volume 1
Energy efficient program updating for sensor nodes with flash memory
Proceedings of the 2010 ACM Symposium on Applied Computing
| Hi-index | 0.00 |
Linking is traditionally a batch process that resolves cross-references between object modules and run-time libraries to produce a stand-alone executable image. Because most program changes only involve a small part of the program, we have implemented an incremental linker, named Inclink, that processes only the changed modules. Inclink generates a new executable in time proportional to the size of change; in contrast, a batch linker generates an executable in time proporitonal to the size of the program. To minimize updates to the executable, Inclink allocates extra space for every module. By allocating 24 percent more space in the executable for overflows, Inclink can update a module in place over 97 percent of the time. Measurements show that Inclink is more than an order of magnitude faster than the UNIX [2] batch linker and that 88 percent of all links will take less than 2 s of CPU time on a MicroVAX-2, independent of program size.