This is the mail archive of the
mailing list for the GCC project.
Re: why no gcc3_compiled symbol
- From: Phil Edwards <phil at jaj dot com>
- To: John David Anglin <dave at hiauly1 dot hia dot nrc dot ca>
- Cc: gcc at gcc dot gnu dot org, drow at mvista dot com
- Date: Thu, 1 Aug 2002 13:39:29 -0400
- Subject: Re: why no gcc3_compiled symbol
- References: <200208010021.g710LWED001716@hiauly1.hia.nrc.ca>
On Wed, Jul 31, 2002 at 08:21:32PM +2000, John David Anglin wrote:
> > Debuggers and related tools use it to identify the object.
> I had a question today from a developer working on purify for
> hppa64-hpux. He wanted to know how to identify a gcc compiled
> object. As far as I know, there isn't any direct way. The HP
> compiler/ assembler stick a bunch of stuff into .note. However,
> gcc/binutils doesn't seem to do this.
There's a wishlist PR, c/2676, asking for the command-line options to
be recorded in the object files. I implemented most of it, but there's
no useful way of getting the information back out, because nobody ever
finished writing the BFD/libbfd.a documentation. So the patch rotted.
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace. We seek
not your counsel, nor your arms. Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen. - Samuel Adams