Re: thoughts on a new switch, -print-flags ?

[Phil Edwards <pedwards at disaster dot jaj dot com>]

On Sun, Nov 26, 2000 at 10:18:13PM -0500, Michael Meissner wrote:
> > 
> > That was all before I found that code was already written to do a lot of
> > the work; I didn't want to reinvent the wheel just to add prettier spokes.
> 
> Another way of getting the same information -- compile with -fverbose-asm
> and -save-temps (assuming asm comment characters are defined), and look at the
> asm temp file.

Yes, that's how I discovered this was available.  But that's like -v -Q,
just extra noise if all you want is flag state.

I started on this because one of the maintainers wondered aloud that
"it would be cool if GCC did this," and I found myself agreeing.  If the
maintainers don't use that method enough to remember it, then who would?  :-)


Getting language-specific flags, incidentally, would require a lot of
rearranging and cleanup for very little return (other than cleaner files,
which is nice in and of itself, but not crucial).

I don't see anyone specifically listed in MAINTAINERS as handling "front-end
infrastructure" like gcc.c/toplev.c, so I don't know who would do the
cleanup, or approve a -print-flags patch if I posted it.


-- 
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.