This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC warnings for unused global variables
- From: "David O'Brien" <obrien at FreeBSD dot org>
- To: Mike Stump <mrs at apple dot com>
- Cc: Richard Henderson <rth at redhat dot com>, Kean Johnston <jkj at sco dot com>, "'Joe Buck'" <jbuck at synopsys dot com>, "'Alexander Kabaev'" <kabaev at mail dot ru>, pthomas at suse dot de, ak03 at gte dot com, gcc at gcc dot gnu dot org
- Date: Thu, 8 May 2003 12:42:51 -0700
- Subject: Re: GCC warnings for unused global variables
- Organization: The NUXI BSD Group
- References: <20030502155430.GC48461@dragon.nuxi.com> <4C380DD2-818C-11D7-BD07-003065A77310@apple.com>
- Reply-to: obrien at FreeBSD dot org
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.