GCC warnings for unused global variables

[David O'Brien]

On Thu, May 08, 2003 at 12:36:00PM -0700, Mike Stump wrote:
> >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 ]

One has to be very proactive to have this.  I've done contract work
updating people's old source bases with their custom hacks to recent
releases.  They certainly weren't this proactive.