This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Request for testing/help for the LTO branch


On Wed, 28 Jan 2009, Rainer Orth wrote:

> Rafael Espindola writes:
> 
> > > I suppose you mis-parsed my question: Solaris and IRIX *are* ELF targets
> > > (just not Linux, so using the system linker, not GNU ld).  If I understand
> > > you correctly, they might just work (modulo bugs)?
> > 
> > That should work. You still might need to extend the linker  to
> > support IL in static libraries. We can work with normal .o with the
> > modified collect2 in the branch, but for archives we need linker
> > support.
> 
> Ok, I see.  Maybe we can extend Sun ld to handle that, given that the
> sources are now open via OpenSolaris.
> 
> > > The only other target of interest to me is Tru64 UNIX, which uses ECOFF,
> > > not ELF.  I don't know if that format is extensible enough to store the IL,
> > > but investigating that is low priority for me.
> > 
> > I  would suggest trying to use elf for the IL. For example, while
> > using plugins gold doesn't care what the *input* file format is.
> 
> Unfortunately, gold doesn't even build on non-Linux targets: see PR
> gold/7024.

That actually appears to be a list of issues with non-Linux hosts, not 
non-Linux targets.

I would certainly hope both LTO and gold should work on a wide range of 
non-Linux hosts (if anyone cares to contribute patches for such support), 
including non-ELF hosts, even though restricted to ELF targets at least in 
the case of gold.  libelf definitely works on MinGW and Solaris hosts.

-- 
Joseph S. Myers
joseph@codesourcery.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]