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 middle-end/65912] x_rtl.x_frame_offset not updated after frame related insn deleted Date: Sun, 19 Dec 2021 00:26:51 +0000 [thread overview] Message-ID: <bug-65912-4-e2NZmWvZiC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65912-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65912 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Target Milestone|--- |6.0 Status|NEW |RESOLVED --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- This aarch64 testcase was fixed in GCC 6. There are already many more bug reports about this issue really, see PR 101926. So closing as fixed for GCC 6.
prev parent reply other threads:[~2021-12-19 0:26 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-28 9:40 [Bug rtl-optimization/65912] New: " jiwang at gcc dot gnu.org 2015-04-28 16:25 ` pinskia 2015-06-25 21:23 ` [Bug rtl-optimization/65912] " ramana at gcc dot gnu.org 2015-06-25 21:23 ` ramana at gcc dot gnu.org 2021-12-19 0:26 ` pinskia at gcc dot gnu.org [this message]
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-65912-4-e2NZmWvZiC@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).