"introduce no new bootstrap warning" criteria. was: Loop ivdebugging, patch

[Geoff Keating]

> Date: Sun, 14 Jan 2001 11:30:36 +0000 (GMT)
> From: "Joseph S. Myers" <jsm28@cam.ac.uk>
> cc: <ghazi@caip.rutgers.edu>, <aj@suse.de>, <dewar@gnat.com>,
>         <dkorn@pixelpower.com>, <gcc@gcc.gnu.org>, <robertlipe@usa.net>
> 
> On Sun, 14 Jan 2001, Geoff Keating wrote:
> 
> > Perhaps we could only define -Werror on non-strange-broken platforms?
> >
> > You know, like Linux, Solaris, Cygwin, AIX.  If you do those, you'll
> > cover probably 99% of the GCC developers.
> 
> That will break every time glibc changes in a way that causes warnings.
> 
> e.g., the "macro strcmp used without args" ones aren't reasonably fixable;
> when glibc 2.2 changed the iconv prototype, that caused warnings; glibc
> 2.2.1 causes the "ISO C99 requires rest arguments to be used" warnings
> every place printf is used with just one argument.

... so perhaps we should try to avoid having glibc change like that?
Or perhaps the macro expander should track which macros are defined in
system headers and not produce warnings for them?

-- 
- Geoffrey Keating <geoffk@geoffk.org>