public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/108995] Missed signed integer overflow checks in UBsan? since r8-343-g2bf54d93f159210d
Date: Mon, 06 Mar 2023 12:42:05 +0000 [thread overview]
Message-ID: <bug-108995-4-vgTWl9TbIZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108995-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108995
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Missed signed integer |Missed signed integer
|overflow checks in UBsan? |overflow checks in UBsan?
| |since
| |r8-343-g2bf54d93f159210d
Status|UNCONFIRMED |NEW
CC| |rguenth at gcc dot gnu.org
Ever confirmed|0 |1
Last reconfirmed| |2023-03-06
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
We regress since r8-343-g2bf54d93f159210d.
next prev parent reply other threads:[~2023-03-06 12:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 19:00 [Bug sanitizer/108995] New: Missed signed integer overflow checks in UBsan? qrzhang at gatech dot edu
2023-03-06 12:42 ` marxin at gcc dot gnu.org [this message]
2023-03-07 7:54 ` [Bug sanitizer/108995] Missed signed integer overflow checks in UBsan? since r8-343-g2bf54d93f159210d rguenth at gcc dot gnu.org
2023-03-09 12:57 ` rguenth at gcc dot gnu.org
2023-03-09 13:29 ` cvs-commit at gcc dot gnu.org
2023-03-09 13:30 ` [Bug c/108995] " rguenth 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-108995-4-vgTWl9TbIZ@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).