public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/99739] [11 Regression] missing optimization of a repeated conditional Date: Wed, 24 Mar 2021 09:13:20 +0000 [thread overview] Message-ID: <bug-99739-4-nIgSJI5wv3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99739-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99739 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |11.0 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Whether we handle this or not at -O1 is quite dependent on short-circuiting anyway - we only have jump threading at our hands at -O1 (we could consider enabling non-iterating EVRP). So I'm not sure this is an important regression. At -O2 we end up with <bb 2> [local count: 1073741824]: _7 = i_2(D) != 0; _8 = j_3(D) != 0; _9 = _7 & _8; if (_9 != 0) goto <bb 5>; [50.00%] else goto <bb 3>; [50.00%] <bb 3> [local count: 536870911]: _23 = k_4(D) != 0; _24 = _7 & _23; _11 = _8 & _24; if (_11 != 0) goto <bb 4>; [94.27%] else goto <bb 5>; [5.73%] <bb 4> [count: 0]: __builtin_abort (); <bb 5> [local count: 1073741824]: return; where reassociation leaves redundant _9 on the plate.
next prev parent reply other threads:[~2021-03-24 9:13 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-23 20:56 [Bug tree-optimization/99739] New: " msebor at gcc dot gnu.org 2021-03-24 9:13 ` rguenth at gcc dot gnu.org [this message] 2021-04-27 11:40 ` [Bug tree-optimization/99739] [11/12 " jakub at gcc dot gnu.org 2021-07-28 7:06 ` rguenth at gcc dot gnu.org 2022-04-21 7:49 ` rguenth at gcc dot gnu.org 2023-03-23 17:57 ` pinskia at gcc dot gnu.org 2023-03-23 18:03 ` jakub at gcc dot gnu.org 2023-03-24 8:41 ` cvs-commit at gcc dot gnu.org 2023-05-29 10:04 ` 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-99739-4-nIgSJI5wv3@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).