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/102950] [11/12 Regression] Dead Code Elimination Regression at -O3 (trunk&11.2.0 vs 10.3.0) Date: Thu, 21 Apr 2022 07:50:38 +0000 [thread overview] Message-ID: <bug-102950-4-O5eRkgsTyk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102950-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102950 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|11.3 |11.4 --- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> --- GCC 11.3 is being released, retargeting bugs to GCC 11.4.
next prev parent reply other threads:[~2022-04-21 7:50 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-26 15:21 [Bug tree-optimization/102950] New: [11 " theodort at inf dot ethz.ch 2021-10-27 0:42 ` [Bug tree-optimization/102950] [11/12 " pinskia at gcc dot gnu.org 2021-10-27 2:49 ` hjl.tools at gmail dot com 2021-11-05 19:19 ` amacleod at redhat dot com 2022-01-18 14:38 ` rguenth at gcc dot gnu.org 2022-02-01 8:59 ` roger at nextmovesoftware dot com 2022-04-21 7:50 ` rguenth at gcc dot gnu.org [this message] 2022-05-03 18:45 ` [Bug tree-optimization/102950] [11/12/13 " cvs-commit at gcc dot gnu.org 2022-05-07 20:11 ` [Bug tree-optimization/102950] [11/12 Regression] Dead Code Elimination Regression at -O3 (11.2.0 " roger at nextmovesoftware dot com 2022-11-03 19:01 ` amacleod at redhat dot com
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-102950-4-O5eRkgsTyk@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).