public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "muecker at gwdg dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/113878] New: missed optimization with sanitizer and signed integer overflow Date: Sun, 11 Feb 2024 16:46:34 +0000 [thread overview] Message-ID: <bug-113878-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113878 Bug ID: 113878 Summary: missed optimization with sanitizer and signed integer overflow Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: muecker at gwdg dot de Target Milestone: --- It would be nice if the following example could be optimized better with the sanitizer. Without sanitizer the function is optimized to return 1. With sanitizer I would expect it to only add the test for the underflow condition, but it then fails to optimize well. int test(int x) { if (x > 100) return 1; x -= 10; if (x > 100) return 2; return 1; } https://godbolt.org/z/j4K96v7jn
next reply other threads:[~2024-02-11 16:46 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-11 16:46 muecker at gwdg dot de [this message] 2024-02-11 16:55 ` [Bug sanitizer/113878] " pinskia at gcc dot gnu.org 2024-02-11 17:43 ` uecker at gcc dot gnu.org 2024-02-11 17:54 ` jakub at gcc dot gnu.org 2024-02-11 18:41 ` uecker at gcc dot gnu.org 2024-02-11 18:46 ` jakub at gcc dot gnu.org 2024-02-11 19:16 ` uecker at gcc dot gnu.org 2024-02-11 19:28 ` jakub at gcc dot gnu.org 2024-02-11 20:07 ` uecker at gcc dot gnu.org 2024-02-12 9:00 ` 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-113878-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).