GCC warnings for unused global variables

[David O'Brien]

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)