public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Ronald F. Guilmette" <rfg@monkeys.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: c/2678: gcc/g++ should stick compilation options into the .o file Date: Sun, 29 Apr 2001 11:56:00 -0000 [thread overview] Message-ID: <20010429185600.30400.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR c/2678; it has been noted by GNATS. From: "Ronald F. Guilmette" <rfg@monkeys.com> 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 11:47:39 -0700 In message <20010429055624.A28542@disaster.jaj.com>, you wrote: >On Sat, Apr 28, 2001 at 08:36:49PM -0000, rfg@monkeys.com wrote: >> And I don't think that it would >> be very hard to get the front-end gcc/g++ driver to pass >> ALL compilation options down to cc1 and/or cc1plus. > >We already do... How convenient! >> They >> in turn could easily still the options into a suitable ELF >> section. > >I can't see any obvious documentation of .note sections in the gas source, >and I don't see .command mentioned at all. I wouldn't mind playing with this >idea while waiting on compiles, if you can point me towards some usage docs. My alopogies if my slippery fingers typed in `.command' when I intended to write `.comment'. For documentation of the intended usage and format of data in ELF .note and .comment sections, you will need to refer to the original AT&T docu- mentation of ELF. I know that documentation (in various non-modified and slightly modified forms) is available on the web in various places, because I found it on the web in several places when I went looking for it a couple of months ago. I'll find a URL or two for you if you need them. Just let me know. Stuff that is placed into ELF .note sections is supposed to obey a very well defined format. However stuff in .comment sections is more in the nature of just free-form text lines, I believe. I can't remember anymore. What gets put into a .note section is basically 100% implementation defined, but when I glanced again at the original AT&T documentation on ELF the other day, it appears to me that the contents of .note is supposed to be, in effect, a set of name/value pairs (vaguely reminicent of UNIX environment variables). The required ``structure'' of the .note section just tells you where and how to encode one of these name/value pairs, in general.
next reply other threads:[~2001-04-29 11:56 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-04-29 11:56 Ronald F. Guilmette [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-05 9:16 Wolfgang Bangerth 2002-11-05 9:08 bangerth 2002-11-05 9:06 Phil Edwards 2002-11-05 7:46 Wolfgang Bangerth 2001-05-07 16:56 Phil Edwards 2001-04-30 17:36 Ronald F. Guilmette 2001-04-30 17:16 Phil Edwards 2001-04-30 10:26 Ronald F. Guilmette 2001-04-30 9:46 Ronald F. Guilmette 2001-04-30 2:36 Phil Edwards 2001-04-30 2:16 Ronald F. Guilmette 2001-04-29 20:06 Phil Edwards 2001-04-29 5:46 Phil Edwards 2001-04-29 5:16 Phil Edwards 2001-04-29 4:16 Phil Edwards 2001-04-28 13:46 rfg
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20010429185600.30400.qmail@sourceware.cygnus.com \ --to=rfg@monkeys.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).