This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [libgo, build] Use convenience libraries to create .gox files
- From: Ian Lance Taylor <iant at google dot com>
- To: Rainer Orth <ro at CeBiTec dot Uni-Bielefeld dot DE>
- Cc: gcc-patches at gcc dot gnu dot org, Ralf Wildenhues <Ralf dot Wildenhues at gmx dot de>, gofrontend-dev at googlegroups dot com
- Date: Wed, 02 Feb 2011 10:45:39 -0800
- Subject: Re: [libgo, build] Use convenience libraries to create .gox files
- References: <yddwrll86oq.fsf@manam.CeBiTec.Uni-Bielefeld.DE> <mcr4o8ok5af.fsf@google.com> <yddsjw6petj.fsf@manam.CeBiTec.Uni-Bielefeld.DE>
Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> writes:
>>> It would be nice if the second step could be implemented using
>>> e.g. simple-object to avoid the external dependency. Any suggestions on
>>> how to handle .go_object on non-ELF platforms without named sections
>>> (Tru64 UNIX with ECOFF in my case)? I suppose I should have a look at
>>> LTO on PE-COFF for ideas.
>>
>> Hmmm, ECOFF is going to be tricky. Unlike COFF, ECOFF does not support
>> arbitrary section names. Offhand I don't know how it could be made to
>> work.
>
> I just had a look at the Tru64 UNIX Object File and Symbol Table Format
> Specification: it seems that the .comment section could be used for this
> purpose:
>
> http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/V51B_HTML/SUPPDOCS/OBJSPEC/NV150XXX.HTM
Looks promising. I hope we don't have to worry about Tru64 before
version 5.1. How do you tell the assembler to put arbitrary data into a
comment subsection? How would you feel about extending the
simple-object interface to pull in comment subsections from Tru64 files?
Ian