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/106570] [12/13 Regression] DCE sometimes fails with depending if statements since r12-2305-g398572c1544d8b75 Date: Sat, 11 Mar 2023 17:07:31 +0000 [thread overview] Message-ID: <bug-106570-4-je4ckiOTgC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106570-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106570 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |needs-bisection Known to fail| |12.1.0 Known to work| |11.1.0 --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Note on the trunk, now the first example fails at -O2 and not just -O3. It might be useful to do a bisect there too. The second example failed for -O2 for GCC 12 too.
next prev parent reply other threads:[~2023-03-11 17:07 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-09 11:35 [Bug tree-optimization/106570] New: DCE sometimes fails with depending if statements tmayerl at student dot ethz.ch 2022-08-09 13:15 ` [Bug tree-optimization/106570] [12/13 Regression] DCE sometimes fails with depending if statements since r12-2305-g398572c1544d8b75 marxin at gcc dot gnu.org 2022-08-09 13:28 ` amacleod at redhat dot com 2022-08-09 13:48 ` rguenth at gcc dot gnu.org 2022-08-10 13:53 ` rguenth at gcc dot gnu.org 2023-03-11 17:07 ` pinskia at gcc dot gnu.org [this message] 2023-03-14 13:16 ` marxin at gcc dot gnu.org 2023-05-08 12:25 ` [Bug tree-optimization/106570] [12/13/14 " rguenth at gcc dot gnu.org 2023-07-13 18:38 ` pinskia 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-106570-4-je4ckiOTgC@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).