From: me22 <me22.ca@gmail.com>
To: Agner Fog <agner@agner.org>
Cc: Ian Lance Taylor <iant@google.com>, gcc-help@gcc.gnu.org
Subject: Re: Is it OK that gcc optimizes away overflow check?
Date: Mon, 25 Jul 2011 17:18:00 -0000 [thread overview]
Message-ID: <CADST3A61z+qKnFDd9xDCCxezYNMkS2AYWbvEj4YCZcoaZg1LPg@mail.gmail.com> (raw)
In-Reply-To: <4E2D29DE.7060308@agner.org>
On Mon, Jul 25, 2011 at 01:31, Agner Fog <agner@agner.org> wrote:
>
> My point is that you are over-interpreting the standard when you conclude
> that the compiler is allowed to do anything in case of overflow.
>
How is signed overflow any different from dereferencing a null
pointer? UB is UB.
next prev parent reply other threads:[~2011-07-25 17:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-23 20:14 Agner Fog
2011-07-23 21:06 ` Jeffrey Walton
2011-07-25 6:07 ` Ian Lance Taylor
2011-07-25 6:04 ` Ian Lance Taylor
2011-07-25 8:32 ` Agner Fog
2011-07-25 17:18 ` me22 [this message]
2011-07-25 17:50 ` Ian Lance Taylor
2011-07-26 9:39 ` Agner Fog
2011-07-26 10:35 ` Andrew Haley
2011-07-26 17:31 ` Andrew Haley
2011-07-27 15:03 ` Agner Fog
2011-07-26 14:55 ` Jeffrey Walton
[not found] ` <4E2E6CC6.3040106@agner.org>
2011-07-26 14:44 ` Ian Lance Taylor
2011-07-26 16:24 ` Agner Fog
2011-07-26 18:17 ` Ian Lance Taylor
2011-07-25 9:43 ` Andrew Haley
2011-07-25 15:38 ` Agner Fog
2011-07-25 16:22 ` Andrew Haley
2011-07-30 23:30 ` Vincent Lefevre
2011-08-01 8:59 ` Andrew Haley
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=CADST3A61z+qKnFDd9xDCCxezYNMkS2AYWbvEj4YCZcoaZg1LPg@mail.gmail.com \
--to=me22.ca@gmail.com \
--cc=agner@agner.org \
--cc=gcc-help@gcc.gnu.org \
--cc=iant@google.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).