Re: c/2678: gcc/g++ should stick compilation options into the .o file

[Phil Edwards <pedwards@disaster.jaj.com>]

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, 30 Apr 2001 04:07:40 -0400

 On Mon, Apr 30, 2001 at 09:16:00AM -0000, Ronald F. Guilmette wrote:
 >  >After some sleep, I've concluded that my original idea of using the
 >  >print_switch_values routine might be stupid.  I don't think people would like
 [...]
 >  >showing up in their object files, for example.  (Or do you?)
 >  
 >  Yes, it would be perfectly OK to put that all into a .comment or .note
 >  section.  Those sections DO NOT get loaded into main memory at run time,
 >  and if necessary, `strip' and be used to remove them after the .o is built.
 
 I know they don't have SHF_ALLOC set, I was concerned with diskspace.
 Which is probably cheap enough to not be worth caring about, on further
 reflection.
 
 For that matter, I had planned to have this controlled by a flag,
 on by default.  People really low on space can always use the flag.
 (something like -fno-note-options)
 
 -- 
 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.