public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kristerw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/106990] New: Missing TYPE_OVERFLOW_SANITIZED checks in match.pd Date: Tue, 20 Sep 2022 23:34:26 +0000 [thread overview] Message-ID: <bug-106990-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106990 Bug ID: 106990 Summary: Missing TYPE_OVERFLOW_SANITIZED checks in match.pd Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: kristerw at gcc dot gnu.org Target Milestone: --- When UBSan is used, match.pd disables simplifications that can remove UB. But two simplifications are missing TYPE_OVERFLOW_SANITIZED checks, making the two tests below fail to report UB when compiled with -fsanitize=undefined. /* (~X - ~Y) -> Y - X. */ int main(void) { volatile int x = -1956816001; volatile int y = 1999200512; return ~x - ~y; } /* -x & 1 -> x & 1. */ int main(void) { volatile int x = 0x80000000; return -x & 1; }
next reply other threads:[~2022-09-20 23:34 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-20 23:34 kristerw at gcc dot gnu.org [this message] 2022-09-21 8:11 ` [Bug tree-optimization/106990] " marxin at gcc dot gnu.org 2022-09-21 8:12 ` rguenth at gcc dot gnu.org 2022-10-18 14:26 ` jakub at gcc dot gnu.org 2022-10-19 9:29 ` cvs-commit at gcc dot gnu.org 2022-10-19 9:31 ` jakub 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-106990-4@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: linkBe 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).