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 rtl-optimization/99199] [11/12/13/14 Regression] Very large boolean expression leads to quite a few return statements Date: Sat, 02 Sep 2023 21:15:44 +0000 [thread overview] Message-ID: <bug-99199-4-afqBrLdc3I@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99199-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99199 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pinskia at gcc dot gnu.org --- Comment #11 from Andrew Pinski <pinskia at gcc dot gnu.org> --- <bb 5> [local count: 234881022]: _1 = ~u_163(D); _2 = _1 & v_164(D); if (_2 != 0) goto <bb 40>; [50.00%] else goto <bb 6>; [50.00%] <bb 6> [local count: 55050240]: _357 = ~v_164(D); _363 = u_163(D) & _357; if (_363 != 0) goto <bb 40>; [53.57%] else goto <bb 7>; [46.43%] This is literally just if (u != v) goto <bb 40>; else goto <bb 7>; ``` int f0(_Bool u, _Bool v) { _Bool t1, t; t = !u & v; t1 = !v & u; if (t) goto L40; if (t1) goto L40; return 0; L40: return 1; } int f1(_Bool u, _Bool v) { _Bool t1, t; t = !u & v; if (t) goto L40; t1 = !v & u; if (t1) goto L40; return 0; L40: return 1; } ``` These should give the same result but don't. Let me file that as a seperate bug ...
next prev parent reply other threads:[~2023-09-02 21:15 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-22 14:16 [Bug tree-optimization/99199] New: [9/10/11 " tkoenig at gcc dot gnu.org 2021-02-22 14:17 ` [Bug tree-optimization/99199] " tkoenig at gcc dot gnu.org 2021-02-22 14:52 ` jakub at gcc dot gnu.org 2021-02-22 16:47 ` jakub at gcc dot gnu.org 2021-02-23 8:15 ` [Bug rtl-optimization/99199] " rguenth at gcc dot gnu.org 2021-02-26 11:55 ` rguenth at gcc dot gnu.org 2021-04-27 11:40 ` [Bug rtl-optimization/99199] [9/10/11/12 " jakub at gcc dot gnu.org 2021-07-28 7:05 ` rguenth at gcc dot gnu.org 2021-12-16 7:32 ` pinskia at gcc dot gnu.org 2021-12-16 7:37 ` pinskia at gcc dot gnu.org 2021-12-16 8:39 ` jakub at gcc dot gnu.org 2022-04-21 7:48 ` rguenth at gcc dot gnu.org 2023-05-29 10:04 ` [Bug rtl-optimization/99199] [10/11/12/13/14 " jakub at gcc dot gnu.org 2023-09-02 21:15 ` pinskia at gcc dot gnu.org [this message] 2024-03-11 2:48 ` [Bug rtl-optimization/99199] [11 " law 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-99199-4-afqBrLdc3I@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).