public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/105086] [12 Regression] Dead Code Elimination Regression at -Os (trunk vs. 11.2.0) 25 Date: Mon, 28 Mar 2022 17:11:33 +0000 [thread overview] Message-ID: <bug-105086-4-4p1VmJC5Rq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105086-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105086 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 |P1 CC| |amacleod at redhat dot com, | |jakub at gcc dot gnu.org Target Milestone|--- |12.0 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Last reconfirmed| |2022-03-28 Summary|Dead Code Elimination |[12 Regression] Dead Code |Regression at -Os (trunk |Elimination Regression at |vs. 11.2.0) 25 |-Os (trunk vs. 11.2.0) 25 --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Started with r12-4871-g502ffb1f389011b28ee51815242c7397790802d5
next prev parent reply other threads:[~2022-03-28 17:11 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-28 17:06 [Bug tree-optimization/105086] New: " yann at ywg dot ch 2022-03-28 17:11 ` jakub at gcc dot gnu.org [this message] 2022-03-28 20:07 ` [Bug tree-optimization/105086] [12 Regression] " amacleod at redhat dot com 2022-03-29 7:31 ` rguenth at gcc dot gnu.org 2022-03-29 13:24 ` amacleod at redhat dot com 2022-03-29 13:37 ` jakub at gcc dot gnu.org 2022-03-29 13:41 ` amacleod at redhat dot com 2022-04-19 15:37 ` rguenth at gcc dot gnu.org 2022-05-06 8:33 ` [Bug tree-optimization/105086] [12/13 " jakub at gcc dot gnu.org 2023-05-08 12:24 ` [Bug tree-optimization/105086] [12/13/14 " rguenth 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-105086-4-4p1VmJC5Rq@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).