public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "acoplan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/100305] ICE in output_operand_lossage with -march=armv8.2-a -O3 Date: Wed, 28 Apr 2021 06:26:51 +0000 [thread overview] Message-ID: <bug-100305-4-p41wM72wJn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100305-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100305 Alex Coplan <acoplan at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Keywords| |ice-on-valid-code Known to fail| |12.0 Last reconfirmed| |2021-04-28 Ever confirmed|0 |1 --- Comment #2 from Alex Coplan <acoplan at gcc dot gnu.org> --- Here is a reduced testcase: typedef double c[3]; typedef int d[3]; typedef struct { d e; } f; typedef struct { f g; f h; } i; i j; double k; int l; void w(void *); void x(char); void u(void *, void *); void m() { char a[4096], n[4096], b[4096], o[4096], p[4096], s[4096], r[4096], t[4096]; w(t); w(p); w(n); w(b); u(a, s); char v = r[0]; c g; { int q[4096]; w(q); w(o); } x(v); l = 0; for (; l < 3; l++) { j.g.e[l] = g[l]; j.h.e[l] = k; } }
next prev parent reply other threads:[~2021-04-28 6:26 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-28 6:13 [Bug c++/100305] New: " gilles.gouaillardet at gmail dot com 2021-04-28 6:25 ` [Bug c++/100305] " acoplan at gcc dot gnu.org 2021-04-28 6:26 ` acoplan at gcc dot gnu.org [this message] 2021-04-28 6:27 ` acoplan at gcc dot gnu.org 2021-04-28 7:47 ` [Bug target/100305] [11/12 Regression] aarch64: ICE in output_operand_lossage with -O3 gilles.gouaillardet at gmail dot com 2021-04-28 7:50 ` pinskia at gcc dot gnu.org 2021-04-28 8:05 ` pinskia at gcc dot gnu.org 2021-04-28 9:50 ` rsandifo at gcc dot gnu.org 2021-04-28 16:55 ` cvs-commit at gcc dot gnu.org 2021-04-28 16:58 ` [Bug target/100305] [10/11/12 " rsandifo at gcc dot gnu.org 2021-04-29 8:28 ` cvs-commit at gcc dot gnu.org 2021-04-29 9:44 ` [Bug target/100305] [10 " cvs-commit at gcc dot gnu.org 2021-04-29 9:45 ` cvs-commit at gcc dot gnu.org 2021-04-30 1:40 ` gilles.gouaillardet at gmail dot com 2021-04-30 14:18 ` rsandifo at gcc dot gnu.org 2021-07-28 7:06 ` rguenth at gcc dot gnu.org 2021-08-17 14:14 ` cvs-commit at gcc dot gnu.org 2021-08-17 14:16 ` rsandifo 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-100305-4-p41wM72wJn@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).