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 target/103396] [GCN][BUILD] ICE RTL check: access of elt 4 of vector with last elt 3 in move_callee_saved_registers, at config/gcn/gcn.c:2821 Date: Tue, 23 Nov 2021 21:16:37 +0000 [thread overview] Message-ID: <bug-103396-4-J9f20h0d6A@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103396-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103396 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Is the cross compiler built with this GCC that includes this patch or this patch just exposing a bug in the backend?
next prev parent reply other threads:[~2021-11-23 21:16 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-23 20:48 [Bug target/103396] New: " burnus at gcc dot gnu.org 2021-11-23 21:13 ` [Bug target/103396] " pinskia at gcc dot gnu.org 2021-11-23 21:16 ` pinskia at gcc dot gnu.org [this message] 2021-11-23 21:20 ` burnus at gcc dot gnu.org 2021-11-23 21:25 ` [Bug target/103396] [12 Regression][GCN][BUILD] " burnus at gcc dot gnu.org 2021-11-24 12:30 ` ams at gcc dot gnu.org 2021-11-25 16:05 ` cvs-commit at gcc dot gnu.org 2021-11-25 16:14 ` ams 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-103396-4-J9f20h0d6A@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).