This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: c/2678: gcc/g++ should stick compilation options into the .ofile
- To: nobody at gcc dot gnu dot org
- Subject: Re: c/2678: gcc/g++ should stick compilation options into the .ofile
- From: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- Date: 29 Apr 2001 12:36:00 -0000
- Cc: gcc-prs at gcc dot gnu dot org,
- Reply-To: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
The following reply was made to PR c/2678; it has been noted by GNATS.
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Phil Edwards <pedwards@disaster.jaj.com>
Cc: <gcc-gnats@gcc.gnu.org>
Subject: Re: c/2678: gcc/g++ should stick compilation options into the .o
file
Date: Sun, 29 Apr 2001 13:26:53 +0100 (BST)
On 29 Apr 2001, Phil Edwards wrote:
> > .note is where GCC used to output the useless "01.01" strings for every
> > file. .commment is where it outputs the compiler version string.
>
> I think that's .ident, not .comment. (Was ".command" a typo for ".comment"?)
.ident assembler directives put data in .comment.
Since the original message mentioned both .comment and .command, I think
.command did mean .comment.
Use e.g. "objdump -s -j .comment <some-executable>" to see what's
currently in these sections.
--
Joseph S. Myers
jsm28@cam.ac.uk