public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rfg@monkeys.com To: gcc-gnats@gcc.gnu.org Subject: c/2678: gcc/g++ should stick compilation options into the .o file Date: Sat, 28 Apr 2001 13:46:00 -0000 [thread overview] Message-ID: <20010428203649.2180.qmail@sourceware.cygnus.com> (raw) >Number: 2678 >Category: c >Synopsis: gcc/g++ should stick compilation options into the .o file >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: change-request >Submitter-Id: net >Arrival-Date: Sat Apr 28 13:46:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Ronald F. Guilmette >Release: gcc-2.95.2 >Organization: >Environment: >Description: It would be Really Nice if the gcc and g++ compilers, when compiling for some ELF target (at least) would stick a copy of ALL of the compilation options used during the compile into an ELF .comment or .note section within the resulting .o file. I wish I had a nickle for every time I had a .o file, left over from some build I did a long long time ago (in a galaxy not far away) and I was stuck saying to myself ``I wish I knew what options this thing had been compiled with. I wonder if it was optimized.'' The ELF object file format provides a couple of obvious means (.command and .note sections) for recording this exact infor- mation into each .o file. 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. They in turn could easily still the options into a suitable ELF section. Note that this would also allow for some potentially inter- esting types of retrospective automated analysis of .o files. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-04-28 13:46 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-04-28 13:46 rfg [this message] 2001-04-29 4:16 Phil Edwards 2001-04-29 5:16 Phil Edwards 2001-04-29 5:46 Phil Edwards 2001-04-29 11:56 Ronald F. Guilmette 2001-04-29 20:06 Phil Edwards 2001-04-30 2:16 Ronald F. Guilmette 2001-04-30 2:36 Phil Edwards 2001-04-30 9:46 Ronald F. Guilmette 2001-04-30 10:26 Ronald F. Guilmette 2001-04-30 17:16 Phil Edwards 2001-04-30 17:36 Ronald F. Guilmette 2001-05-07 16:56 Phil Edwards 2002-11-05 7:46 Wolfgang Bangerth 2002-11-05 9:06 Phil Edwards 2002-11-05 9:08 bangerth 2002-11-05 9:16 Wolfgang Bangerth
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=20010428203649.2180.qmail@sourceware.cygnus.com \ --to=rfg@monkeys.com \ --cc=gcc-gnats@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).