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: Bernd Jendrissek <berndj at prism dot co dot za>
- Cc: Bonzini <bonzini at gnu dot org>, gcc at gcc dot gnu dot org
- Date: Mon, 5 May 2003 17:50:06 -0700
- Subject: Re: GCC warnings for unused global variables
- Organization: The NUXI BSD Group
- References: <20030502163455.GD48461@dragon.nuxi.com> <20030505132631.C31156@prism.co.za>
- Reply-to: obrien at FreeBSD dot org
On Mon, May 05, 2003 at 01:26:31PM +0200, Bernd Jendrissek wrote:
> On Fri, May 02, 2003 at 09:34:55AM -0700, David O'Brien wrote:
> > On Fri, May 02, 2003 at 01:42:30PM +0200, Bonzini wrote:
> > > mankind is warned with at least a year of advance, and let's face that
> > > the fix is (more or less) as simple as
> > > grep -rl "^static.*const.*rcsid" | perl -i -pe '!$replaced_yet && s/^static.*const(.*rcsid)/volatile$1/ && ($replaced_yet = 1)'.
> >
> > You've never worked on a large corporate source base have you? Just
> > making the source change is only 1/2 the battle. Getting the review
> > board (or release engineer, or what ever) approval for wide sweeping
> > changes can be quite difficult.
>
> And getting approval to use a different compiler is easy?
It is when you haven't any choice.
> If the legacy code is too "precious" to touch, then just continue to use
> gcc-1.42.
Sorry gcc 1.42 does not generate AMD64 code.
--
-- David (obrien@FreeBSD.org)