|global optimizing compilers vs. unix/make/rcs development methodology email@example.com (1993-08-01)|
|Re: global optimizing vs. unix/make/rcs firstname.lastname@example.org (1993-08-01)|
|From:||email@example.com (Alan Watson)|
|Organization:||University of Wisconsin - Astronomy Department|
|Date:||Sun, 1 Aug 1993 19:21:43 GMT|
firstname.lastname@example.org (merlin) writes:
>Unfortunately, this general procedure makes it impossible for any globally
>optimizing compiler to see any more than a small part of the program which
>it is supposed to be globally optimizing at any one time.
On several systems (DEC/SGI/MIPS MIPS and DEC Alpha, at least), one can
compile modules to ucode, an intermediate form, and then let the ucode
linker and optimizer have at the whole program, in effect. One simply
replaces object files, libraries, and linkers with their corresponding
ucode equivalents, and puts a global optimizer in the ucode linker. As a
user, I'm very happy with it.
Return to the
Search the comp.compilers archives again.