This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: pretty -print.h w arning: ‘_ _gcc_tdiag __’ is an unrecogniz ed format function t ype
ok. 1) my mistake for not reading the FAQ, sorry.
2) add to the FAQ, for the diligent folks who read it? Sorry, good point.
It's tough, you know, bootstrap compilers vary widely in quality. gcc 4.0 pretty good, old vendor cc sometimes really bad, though they are falling out of support (e.g. HP-UX/HPPA K&R-only, Irix, etc.);
I gotta go,
?- Jay
----------------------------------------
> Date: Mon, 11 Jun 2012 20:27:16 +0000
> From: joseph@codesourcery.com
> To: lopezibanez@gmail.com
> CC: jay.krell@cornell.edu; gcc@gcc.gnu.org
> Subject: Re: Re: pretty-print.h warning: ‘__gcc_tdiag__’ is an unrecognized format function type
>
> On Mon, 11 Jun 2012, Manuel López-Ibáñez wrote:
>
> > http://gcc.gnu.org/wiki/FAQ#stage1warnings
> >
> > I really don't understand why first stage or --disable-bootstrap is
> > not using -w. (Probably, like most things in GCC, because nobody has
> > bothered to implement it.)
>
> If you are building a cross compiler (so not bootstrapped), having the
> warnings, even if noisy because the compiler used to build it isn't
> exactly the same version as the compiler being built, is a lot better than
> hiding them all. And if a file fails to build in stage 1 of a bootstrap,
> having the warnings, again even if noisy, helps identify the problem more
> than if only actual error messages are present (more generally, warnings
> from a changed file in stage 1 of a bootstrap give you an early indication
> of possible problems with a patch without needing to wait for a later
> stage for a more precise set).
>
> --
> Joseph S. Myers
> joseph@codesourcery.com