Related articles |
---|
MIPS optimizing compiler brdsutte@elis.rug.ac.be (1997-08-28) |
Re: MIPS optimizing compiler cfc@world.std.com (1997-08-30) |
Re: MIPS optimizing compiler simg@netcom.com (1997-08-30) |
Re: MIPS optimizing compiler fjh@mundook.cs.mu.OZ.AU (1997-09-03) |
Re: MIPS optimizing compiler robert.wilson@Eng.Sun.COM (Bob Wilson) (1997-09-07) |
From: | Bob Wilson <robert.wilson@Eng.Sun.COM> |
Newsgroups: | comp.compilers |
Date: | 7 Sep 1997 15:00:26 -0400 |
Organization: | WorkShop Developer Products, Sun Microsystems |
References: | 97-08-079 97-08-089 97-09-008 |
Keywords: | linker |
Fergus Henderson wrote:
>
> The flaws in the SGI/MIPS implementation mentioned above are all
> addressable. Link-time optimization information can be placed in (a
> special section of) standard object files, so that existing makefiles
> do not need to be modified. There is no need to require the use of a
> different code model (ABI) in order to use link-time optimizations.
> The use of link-time optimizations need not prevent the use of DSOs.
It's ironic that everyone is identifying SGI/MIPS with the old ucode
style of link-time optimization, since SGI/MIPS has already
implemented and shipped a compiler that does what Fergus suggests.
With certain options, the MIPSpro compilers will produce special ELF
object files that contain all the high-level intermediate
representation necessary for link-time optimizations. The actual code
generation doesn't happen until link-time, but since the object files
look like standard .o files you don't need to completely rewrite your
makefiles.
-----------------------------------------------------------------
Bob Wilson
Authoring and Development Tools, Sun Microsystems, Inc.
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.