From: Ian Lance Taylor <iant@google.com>
To: "Richard Guenther" <richard.guenther@gmail.com>
Cc: "Jakub Jelinek" <jakub@redhat.com>,
"Mark Mitchell" <mark@codesourcery.com>,
gcc-patches@gcc.gnu.org
Subject: Re: PATCH RFC: Warn about pointer wraparound with -Wstrict-overflow
Date: Tue, 08 Apr 2008 22:16:00 -0000 [thread overview]
Message-ID: <m3skxwqah6.fsf@google.com> (raw)
In-Reply-To: <84fc9c000804081359n75fbd0f1j17aea54404e9696e@mail.gmail.com> (Richard Guenther's message of "Tue\, 8 Apr 2008 22\:59\:37 +0200")
"Richard Guenther" <richard.guenther@gmail.com> writes:
> How about some C++ code using libstdc++? (of course #pragma system_header
> may save our day here)
I built libstdc++ itself, and got two warnings with
-Wstrict-overflow=3, neither of which were a pointer wraparound
warning.
Ian
next prev parent reply other threads:[~2008-04-08 21:54 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 20:46 Ian Lance Taylor
2008-04-08 9:31 ` Richard Guenther
2008-04-08 15:16 ` Ian Lance Taylor
2008-04-08 16:31 ` Richard Guenther
2008-04-08 18:15 ` Ian Lance Taylor
2008-04-11 10:04 ` gsan
2008-04-14 19:34 ` Ian Lance Taylor
2008-04-08 18:59 ` Mark Mitchell
2008-04-08 19:01 ` Ian Lance Taylor
2008-04-08 19:08 ` Mark Mitchell
2008-04-08 21:00 ` Ian Lance Taylor
2008-04-08 23:50 ` Mark Mitchell
2008-04-08 19:40 ` Jakub Jelinek
2008-04-08 21:08 ` Ian Lance Taylor
2008-04-08 21:18 ` Richard Guenther
2008-04-08 22:16 ` Ian Lance Taylor [this message]
2008-04-08 20:57 ` Richard Guenther
2008-04-08 21:47 ` Paul Brook
2008-04-08 21:54 ` Andrew Pinski
2008-04-08 21:54 ` Mark Mitchell
2008-04-08 21:56 ` Richard Guenther
2008-04-08 23:48 ` Mark Mitchell
2008-04-10 18:22 ` Joseph S. Myers
2008-04-14 20:02 ` PATCH COMMITTED: " Ian Lance Taylor
2008-04-15 9:26 ` Richard Guenther
2008-04-15 14:28 ` Ian Lance Taylor
2008-04-15 17:49 ` Ian Lance Taylor
2008-04-17 6:24 ` Ian Lance Taylor
2008-04-18 16:22 ` Ian Lance Taylor
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=m3skxwqah6.fsf@google.com \
--to=iant@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=mark@codesourcery.com \
--cc=richard.guenther@gmail.com \
/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).