"Tom Browder" <tom.browder@xxxxxxxxx> writes: > On Mon, Dec 29, 2008 at 3:30 PM, Ian Lance Taylor <iant@xxxxxxxxxx> wrote: > ... >> Sorry, I didn't quite understand your question. In general we gcc >> developers don't want to suppress warnings that occur when building >> gcc. In fact, during development we use -Werror, making all warnings >> be errors, so normally gcc builds with no warnings at all. Of course, > > I'll go back and redo my last build and look at the warnings, but I'm > pretty sure I see mostly the usual warnings about comparison of signed > versus unsigned and such that are probably due to developer > optimizations, but they are bothersome. It is normal to see warnings when compiling one version of gcc with a different version of gcc. Warnings are turned into errors when compiling one version of gcc with the same version, which normally occurs in the second and third stage of the bootstrap which is part of the standard build and install procedure. Ian
