public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/106210] [10/11/12/13 Regression] missing shrink wrap for simple case since r9-3594-g8d2d39587d941a40 Date: Mon, 18 Jul 2022 08:00:55 +0000 [thread overview] Message-ID: <bug-106210-4-prX1oHPMrw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106210-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106210 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |segher at gcc dot gnu.org Keywords|needs-bisection | Summary|[10/11/12/13 Regression] |[10/11/12/13 Regression] |missing shrink wrap for |missing shrink wrap for |simple case |simple case since | |r9-3594-g8d2d39587d941a40 --- Comment #5 from Martin Liška <marxin at gcc dot gnu.org> --- All right, then it started with r9-3594-g8d2d39587d941a40.
next prev parent reply other threads:[~2022-07-18 8:00 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-05 22:39 [Bug rtl-optimization/106210] New: missing shrink wrap for simple case pinskia at gcc dot gnu.org 2022-07-05 22:43 ` [Bug rtl-optimization/106210] [10/11/12/13 Regression] " pinskia at gcc dot gnu.org 2022-07-05 22:48 ` pinskia at gcc dot gnu.org 2022-07-15 8:36 ` marxin at gcc dot gnu.org 2022-07-15 19:32 ` pinskia at gcc dot gnu.org 2022-07-18 8:00 ` marxin at gcc dot gnu.org [this message] 2022-07-18 17:34 ` [Bug rtl-optimization/106210] [10/11/12/13 Regression] missing shrink wrap for simple case since r9-3594-g8d2d39587d941a40 segher at gcc dot gnu.org 2022-10-19 10:36 ` rguenth at gcc dot gnu.org 2023-07-07 10:43 ` [Bug rtl-optimization/106210] [11/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-106210-4-prX1oHPMrw@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).