From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Haoxin Tu <haoxintu@gmail.com>
Cc: GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: Possible wrong-code bug in GCC?
Date: Tue, 2 Aug 2022 07:35:43 +0100 [thread overview]
Message-ID: <CAH6eHdRos6mAoCvOz9T7RcM61z7ywXcx0NHQWEQoiUWB3y8rLw@mail.gmail.com> (raw)
In-Reply-To: <CALDyosZzYJ9MTxroe9mfH+3cgmnnUUajQm6Dw+1+1W6-q6QVRA@mail.gmail.com>
On Tue, 2 Aug 2022 at 05:45, Haoxin Tu via Gcc <gcc@gcc.gnu.org> wrote:
>
> Oh, sorry for the noise, there is an integer overflow that may cause
> undefined behavior.
You should check with UBsan before reporting something as a bug:
s.c:5:2: runtime error: signed integer overflow: 2147483647 + 1 cannot
be represented in type 'int'
prev parent reply other threads:[~2022-08-02 6:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 3:23 Haoxin Tu
2022-08-02 4:44 ` Haoxin Tu
2022-08-02 6:35 ` Jonathan Wakely [this message]
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=CAH6eHdRos6mAoCvOz9T7RcM61z7ywXcx0NHQWEQoiUWB3y8rLw@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=haoxintu@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).