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/105834] [13/14 Regression] Dead Code Elimination Regression at -O2 (trunk vs. 12.1.0) Date: Thu, 13 Jul 2023 20:26:53 +0000 [thread overview] Message-ID: <bug-105834-4-TA7XwUujnd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105834-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105834 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |needs-bisection Known to work| |14.0 --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Looks to be fixed on the trunk. We also now get from evrp: Global Exported: c_5 = [irange] int [0, 0][3, 3]
next prev parent reply other threads:[~2023-07-13 20:26 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-03 13:25 [Bug tree-optimization/105834] New: " theodort at inf dot ethz.ch 2022-06-13 12:36 ` [Bug tree-optimization/105834] [13 Regression] " rguenth at gcc dot gnu.org 2023-02-21 14:23 ` rguenth at gcc dot gnu.org 2023-02-21 22:25 ` pinskia at gcc dot gnu.org 2023-04-08 14:43 ` law at gcc dot gnu.org 2023-04-26 6:56 ` [Bug tree-optimization/105834] [13/14 " rguenth at gcc dot gnu.org 2023-07-13 20:26 ` pinskia at gcc dot gnu.org [this message] 2023-07-27 9:23 ` rguenth at gcc dot gnu.org 2023-11-05 22:05 ` tkoenig at gcc dot gnu.org 2023-11-07 8:26 ` [Bug tree-optimization/105834] [13 " rguenth at gcc dot gnu.org 2024-05-21 9:11 ` 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-105834-4-TA7XwUujnd@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).