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 tree-optimization/113879] New: missed optimization - not exploiting known range of integers Date: Sun, 11 Feb 2024 20:01:31 +0000 [thread overview] Message-ID: <bug-113879-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113879 Bug ID: 113879 Summary: missed optimization - not exploiting known range of integers Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: muecker at gwdg dot de Target Milestone: --- This is similar to PR105855 but without sanitizer. In the following example the loop is not vectorized because the overflow check (which is not needed) is not removed. It works when adding the first check before the loop. But the information about j < INT_MAX can be derived directly from j < i + 4. void f(int i, float * restrict a, float * restrict b) { #if 0 if (INT_MAX - 4 < i) __builtin_unreachable(); #endif for (int j = i; j < i + 4; ) { a[j] = b[j] + 1.; #if 1 if (INT_MAX - 1 < j) __builtin_trap(); #endif j++; } } https://godbolt.org/z/xnEbh5zfv
next reply other threads:[~2024-02-11 20:01 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-11 20:01 muecker at gwdg dot de [this message] 2024-02-12 9:04 ` [Bug tree-optimization/113879] " rguenth at gcc dot gnu.org 2024-02-12 16:01 ` amacleod at redhat dot com 2024-05-23 20:53 ` cvs-commit 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-113879-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).