public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/107890] UB on integer overflow impacts code flow
Date: Sun, 27 Nov 2022 21:36:35 +0000 [thread overview]
Message-ID: <bug-107890-4-BfiFsZNCXc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107890-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107890
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|UNCONFIRMED |RESOLVED
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
>I was under the impression that this kind of undefined behavior essentially meant that the value of that integer could become unreliable.
Your impression is incorrect. Once undefined behavior happens, anything can
happen.
This is why things like -fsanitize=undefined is there now.
next prev parent reply other threads:[~2022-11-27 21:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-27 21:31 [Bug c/107890] New: " gcc at pkh dot me
2022-11-27 21:36 ` pinskia at gcc dot gnu.org [this message]
2022-11-28 1:02 ` [Bug c/107890] " redi at gcc dot gnu.org
2022-11-28 7:51 ` muecker at gwdg dot de
2022-11-28 8:26 ` pinskia at gcc dot gnu.org
2022-12-01 7:44 ` egallager at gcc dot gnu.org
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=bug-107890-4-BfiFsZNCXc@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).