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 c/100536] New: ICE: in expand_call, at calls.c:4980 Date: Tue, 11 May 2021 16:20:28 +0000 [thread overview] Message-ID: <bug-100536-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100536 Bug ID: 100536 Summary: ICE: in expand_call, at calls.c:4980 Product: gcc Version: tree-ssa Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: cnsun at uwaterloo dot ca Target Milestone: --- $ gcc-trunk -v Using built-in specs. COLLECT_GCC=gcc-trunk COLLECT_LTO_WRAPPER=/scratch/software/gcc-trunk/libexec/gcc/x86_64-pc-linux-gnu/12.0.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /tmp/tmp.FUbEknNORK-gcc-builder/gcc/configure --enable-languages=c,c++,lto --enable-checking-yes --enable-multiarch --prefix=/scratch/software/gcc-trunk --disable-bootstrap Thread model: posix Supported LTO compression algorithms: zlib gcc version 12.0.0 20210511 (experimental) [master revision :7db32cac8:aa891c56f25baac94db004e309d1b6e40b770a95] (GCC) $ cat mutant.c struct { union { union { union { union { union { union { double b[4]; } a[18]; } a[18]; } a[18]; } a[18]; } a[18]; } a[18]; } s; baz() { bar(s); } $ gcc-trunk mutant.c mutant.c:16:1: warning: return type defaults to ‘int’ [-Wimplicit-int] 16 | baz() { bar(s); } | ^~~ mutant.c: In function ‘baz’: mutant.c:16:9: warning: implicit declaration of function ‘bar’; did you mean ‘baz’? [-Wimplicit-function-declaration] 16 | baz() { bar(s); } | ^~~ | baz mutant.c:16:9: sorry, unimplemented: passing too large argument on stack 16 | baz() { bar(s); } | ^~~~~~ during RTL pass: expand mutant.c:16:9: internal compiler error: in expand_call, at calls.c:4980 0x686a4e expand_call(tree_node*, rtx_def*, int) /tmp/tmp.FUbEknNORK-gcc-builder/gcc/gcc/calls.c:4980 0xb5fe9e expand_expr_real_1(tree_node*, rtx_def*, machine_mode, expand_modifier, rtx_def**, bool) /tmp/tmp.FUbEknNORK-gcc-builder/gcc/gcc/expr.c:11461 0xa3cfc9 expand_expr /tmp/tmp.FUbEknNORK-gcc-builder/gcc/gcc/expr.h:301 0xa3cfc9 expand_call_stmt /tmp/tmp.FUbEknNORK-gcc-builder/gcc/gcc/cfgexpand.c:2843 0xa3cfc9 expand_gimple_stmt_1 /tmp/tmp.FUbEknNORK-gcc-builder/gcc/gcc/cfgexpand.c:3847 0xa3cfc9 expand_gimple_stmt /tmp/tmp.FUbEknNORK-gcc-builder/gcc/gcc/cfgexpand.c:4011 0xa428c9 expand_gimple_basic_block /tmp/tmp.FUbEknNORK-gcc-builder/gcc/gcc/cfgexpand.c:6048 0xa4451f execute /tmp/tmp.FUbEknNORK-gcc-builder/gcc/gcc/cfgexpand.c:6732 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions.
next reply other threads:[~2021-05-11 16:20 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-11 16:20 cnsun at uwaterloo dot ca [this message] 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 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@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).