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/100526] New: ICE: segmentation fault in gimple-parser.c2049 Date: Tue, 11 May 2021 15:28:25 +0000 [thread overview] Message-ID: <bug-100526-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100526 Bug ID: 100526 Summary: ICE: segmentation fault in gimple-parser.c2049 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 __GIMPLE foo() { enum tst; } $ gcc-trunk -O0 mutant.c mutant.c:1:1: error: ‘__GIMPLE’ only valid with ‘-fgimple’ 1 | __GIMPLE | ^~~~~~~~ mutant.c:2:1: warning: return type defaults to ‘int’ [-Wimplicit-int] 2 | foo() { enum tst; } | ^~~ mutant.c: In function ‘foo’: mutant.c:2:17: error: expected identifier or ‘(’ before ‘;’ token 2 | foo() { enum tst; } | ^ mutant.c:2:17: internal compiler error: Segmentation fault 0xef7273 crash_signal /tmp/tmp.FUbEknNORK-gcc-builder/gcc/gcc/toplev.c:327 0x9528a8 c_parser_gimple_declaration /tmp/tmp.FUbEknNORK-gcc-builder/gcc/gcc/c/gimple-parser.c:2049 0x9528a8 c_parser_gimple_compound_statement /tmp/tmp.FUbEknNORK-gcc-builder/gcc/gcc/c/gimple-parser.c:391 0x954fa7 c_parser_parse_gimple_body(c_parser*, char*, c_declspec_il, profile_count) /tmp/tmp.FUbEknNORK-gcc-builder/gcc/gcc/c/gimple-parser.c:253 0x944187 c_parser_declaration_or_fndef /tmp/tmp.FUbEknNORK-gcc-builder/gcc/gcc/c/c-parser.c:2533 0x94b9d3 c_parser_external_declaration /tmp/tmp.FUbEknNORK-gcc-builder/gcc/gcc/c/c-parser.c:1777 0x94c439 c_parser_translation_unit /tmp/tmp.FUbEknNORK-gcc-builder/gcc/gcc/c/c-parser.c:1650 0x94c439 c_parse_file() /tmp/tmp.FUbEknNORK-gcc-builder/gcc/gcc/c/c-parser.c:21984 0x9ac765 c_common_parse_file() /tmp/tmp.FUbEknNORK-gcc-builder/gcc/gcc/c-family/c-opts.c:1218 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 15:28 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-11 15:28 cnsun at uwaterloo dot ca [this message] 2021-12-12 6:28 ` [Bug c/100526] " 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-100526-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).