GCC warnings for unused global variables

[Mike Stump]

On Friday, May 2, 2003, at 08:54 AM, David O'Brien wrote:
> On Thu, May 01, 2003 at 11:42:57AM -0700, Richard Henderson wrote:
>> On Thu, May 01, 2003 at 10:54:44AM -0700, Kean Johnston wrote:
>>> I am frankly surprised you don't see that and are fighting
>>> so hard for this to stay in -Wall.
>>
>> Perhaps a personal bias.  I've always *hated* rcsid tags.
>
> I hate to say it, but *HATE* that GCC source file have no way of 
> knowing
> which rev they are.  It has been a problem more than once.

They do, just type cvs status file.c.  :-(  If you want source to know 
what version it is, why not have a flag -DVERSION="\"`grep $file 
CVS/Entries`\"" in the .o.c rule?

If you want files under two (or more) different cvs systems, just 
create scripts that link CVS to CVS-name_of_tree through out the whole 
hierarchy?  Simple, easy to do, works like a charm.  I've done stuff 
like this before, it it works really spiffy.

push gcc
cvs status file.c
[ info on what version in the gcc tree file.c came from ]
push freebsd
cvs status file.c
] info on what version in the freebsd tree file.c came from ]