public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Phil Edwards <pedwards@disaster.jaj.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: Mon, 07 May 2001 16:56:00 -0000 [thread overview] Message-ID: <20010507235601.30395.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR c/2678; it has been noted by GNATS. From: Phil Edwards <pedwards@disaster.jaj.com> To: "Ronald F. Guilmette" <rfg@monkeys.com> Cc: gcc-gnats@gcc.gnu.org Subject: Re: c/2678: gcc/g++ should stick compilation options into the .o file Date: Mon, 7 May 2001 18:33:36 -0400 On Tue, May 01, 2001 at 12:36:01AM -0000, Ronald F. Guilmette wrote: > OK. So now _here_ is a good excuse to come up with a new GNU invention... > a new ``GNU standardized'' ELF section name. Given the overly-loose hammer and nail analogy that you sent me in private email, I'll assume you're being facetious here. :-) > Hummm... OK. Wait a minute. That would work, but I have a better idea... > > Just _label_ each one of these hunks of option information with the > specific corresponding .c or .C ``primary'' source file name that was > being compiled when those options were used. Then the final linked > file would, in effect contain essentially a complete history, telling > you how it got built. Hell! You could practically write a program > to automatically reverse-engineer and re-create the original Makefiles > (or files functionally equivalent to them) just from the final linked > executable! Actually, my current implementation already does this. I needed to figure out where an extra copy of the options was coming from, and I left the code in when I was done. And I've never tried writing a tool using the BFD library, but if I understand its purpose correctly, it should be easy to use it to write a build-option-pretty-printer for an executable. It's on that part of my TODO list titled, "probably useless but would be really fun to try."[*] Phil [*] Much of my life is under this category, so there's a good chance that this tool would be written, if I haven't misunderstood BFD. -- pedwards at disaster dot jaj dot com | pme at sources dot redhat dot com devphil at several other less interesting addresses in various dot domains The gods do not protect fools. Fools are protected by more capable fools.
next reply other threads:[~2001-05-07 16:56 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-05-07 16:56 Phil Edwards [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-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 11:56 Ronald F. Guilmette 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=20010507235601.30395.qmail@sourceware.cygnus.com \ --to=pedwards@disaster.jaj.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).