public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cnsun at uwaterloo dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/100536] ICE: in expand_call with large union (1GB) argument
Date: Wed, 12 May 2021 22:56:42 +0000 [thread overview]
Message-ID: <bug-100536-4-6RUq9CYrAl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100536-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100536
--- Comment #3 from Chengnian Sun <cnsun at uwaterloo dot ca> ---
A duplicate here.
typedef struct {
struct {
struct {
struct {
struct {
struct {
struct {
struct {
struct {
struct {
struct {
int f;
} f[8];
} f[8];
} f[8];
} f[8];
} f[8];
} f[8];
} f[8];
} f[8];
} f[8];
} f[8];
} T;
f(w) T *w;
{
int i;
g(w[i]);
}
next prev parent reply other threads:[~2021-05-12 22:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 16:20 [Bug c/100536] New: ICE: in expand_call, at calls.c:4980 cnsun at uwaterloo dot ca
2021-05-11 22:03 ` [Bug middle-end/100536] ICE: in expand_call with large union (1GB) argument pinskia at gcc dot gnu.org
2021-05-12 6:45 ` rguenth at gcc dot gnu.org
2021-05-12 22:56 ` cnsun at uwaterloo dot ca [this message]
2021-07-04 18:21 ` pinskia at gcc dot gnu.org
2022-01-10 21:27 ` k.even-mendoza at imperial dot ac.uk
2022-01-11 1:17 ` pinskia at gcc dot gnu.org
2022-02-28 8:07 ` roger at nextmovesoftware dot com
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-100536-4-6RUq9CYrAl@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: link
Be 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).