public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit 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: Thu, 09 Mar 2023 13:29:49 +0000 [thread overview]
Message-ID: <bug-108995-4-GZZmsY3NNh@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
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:ace65db9215882b95e2ead1bb0dc8c54c2ea69be
commit r13-6550-gace65db9215882b95e2ead1bb0dc8c54c2ea69be
Author: Richard Biener <rguenther@suse.de>
Date: Wed Mar 8 09:06:44 2023 +0100
middle-end/108995 - avoid folding when sanitizing overflow
The following plugs one place in extract_muldiv where it should avoid
folding when sanitizing overflow.
PR middle-end/108995
* fold-const.cc (extract_muldiv_1): Avoid folding
(CST * b) / CST2 when sanitizing overflow and we rely on
overflow being undefined.
* gcc.dg/ubsan/pr108995.c: New testcase.
next prev parent reply other threads:[~2023-03-09 13:29 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 ` [Bug sanitizer/108995] Missed signed integer overflow checks in UBsan? since r8-343-g2bf54d93f159210d marxin at gcc dot gnu.org
2023-03-07 7:54 ` 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 [this message]
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-GZZmsY3NNh@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).