From: Geoff Keating <geoffk@geoffk.org>
To: 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
Subject: Re: "introduce no new bootstrap warning" criteria. was: Loop ivdebugging, patch
Date: Sun, 14 Jan 2001 04:01:00 -0000 [thread overview]
Message-ID: <200101141201.EAA32441@geoffk.org> (raw)
In-Reply-To: <Pine.LNX.4.30.0101141128060.17694-100000@kern.srcf.societies.cam.ac.uk>
> 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>
next prev parent reply other threads:[~2001-01-14 4:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-13 4:34 "introduce no new bootstrap warning" criteria. was: Loop iv debugging, patch Kaveh R. Ghazi
2001-01-13 5:34 ` Andreas Jaeger
2001-01-14 0:22 ` Geoff Keating
2001-01-14 3:31 ` "introduce no new bootstrap warning" criteria. was: Loop ivdebugging, patch Joseph S. Myers
2001-01-14 4:01 ` Geoff Keating [this message]
2001-01-14 4:41 ` "introduce no new bootstrap warning" criteria. was: Loop iv debugging, patch Neil Booth
-- strict thread matches above, loose matches on Subject: below --
2001-01-12 5:50 "introduce no new bootstrap warning" criteria. was: Loop iv debugging patch Robert Lipe
2001-01-12 6:13 ` "introduce no new bootstrap warning" criteria. was: Loop ivdebugging patch Joseph S. Myers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200101141201.EAA32441@geoffk.org \
--to=geoffk@geoffk.org \
--cc=aj@suse.de \
--cc=dewar@gnat.com \
--cc=dkorn@pixelpower.com \
--cc=gcc@gcc.gnu.org \
--cc=ghazi@caip.rutgers.edu \
--cc=jsm28@cam.ac.uk \
--cc=robertlipe@usa.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).