public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/83541] Missed optimization with int overflow Date: Sun, 12 Dec 2021 12:30:34 +0000 [thread overview] Message-ID: <bug-83541-4-g6N4X2Vy3X@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-83541-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83541 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |enhancement Keywords| |needs-bisection Known to work| |12.0 Known to fail| |11.2.0 --- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Seems to be fixed on the trunk. Folding statement: if (x_2(D) == 2147483647) Visiting conditional with predicate: if (x_2(D) == 2147483647) With known ranges x_2(D): int VARYING Predicate evaluates to: DON'T KNOW Matching expression match.pd:2077, gimple-match.c:819 Matching expression match.pd:2080, gimple-match.c:892 Matching expression match.pd:2087, gimple-match.c:952 Not folded Folding statement: _4 = x_2(D) + 1; gimple_simplified to _4 = -2147483648; Folded into: _4 = -2147483648; Folding statement: // predicted unlikely by early return (on trees) predictor. Not folded Folding PHI node: _1 = PHI <_4(3), 42(2)> Queued PHI for removal. Folds to: 42 Folding statement: return _1; Folded into: return 42;
next parent reply other threads:[~2021-12-12 12:30 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-83541-4@http.gcc.gnu.org/bugzilla/> 2021-12-12 12:30 ` pinskia at gcc dot gnu.org [this message] 2022-01-03 9:24 ` rguenth at gcc dot gnu.org 2022-01-12 15:28 ` cvs-commit at gcc dot gnu.org 2022-01-12 15:29 ` amacleod at redhat dot com
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-83541-4-g6N4X2Vy3X@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).