public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/97141] [10 Regression] aarch64, SVE: ICE in decompose, at rtl.h (during expand) since r10-4676-g9c437a108a Date: Wed, 31 Mar 2021 20:37:12 +0000 [thread overview] Message-ID: <bug-97141-4-e4mpHMdTj0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97141-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97141 rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[10/11 Regression] aarch64, |[10 Regression] aarch64, |SVE: ICE in decompose, at |SVE: ICE in decompose, at |rtl.h (during expand) since |rtl.h (during expand) since |r10-4676-g9c437a108a |r10-4676-g9c437a108a --- Comment #5 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> --- Fixed on trunk so far.
next prev parent reply other threads:[~2021-03-31 20:37 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-21 10:48 [Bug target/97141] New: [10/11 " acoplan at gcc dot gnu.org 2020-09-21 11:29 ` [Bug target/97141] " rguenth at gcc dot gnu.org 2020-12-08 14:39 ` akrl at gcc dot gnu.org 2020-12-16 14:10 ` acoplan at gcc dot gnu.org 2021-01-14 9:21 ` rguenth at gcc dot gnu.org 2021-01-14 9:21 ` rguenth at gcc dot gnu.org 2021-03-30 11:05 ` rsandifo at gcc dot gnu.org 2021-03-31 18:34 ` cvs-commit at gcc dot gnu.org 2021-03-31 20:37 ` rsandifo at gcc dot gnu.org [this message] 2021-03-31 20:38 ` [Bug target/97141] [10 " rsandifo at gcc dot gnu.org 2021-04-08 12:02 ` rguenth at gcc dot gnu.org 2021-04-23 9:10 ` cvs-commit at gcc dot gnu.org 2021-04-23 9:14 ` rsandifo at gcc dot gnu.org 2021-12-12 13:18 ` pinskia 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-97141-4-e4mpHMdTj0@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).