public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "evan@coeus-group.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/95782] [ppc64le] ICE in _cpp_pop_context Date: Tue, 25 May 2021 01:28:06 +0000 [thread overview] Message-ID: <bug-95782-4-JoBRmkyanW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95782-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95782 --- Comment #1 from Evan Nemerson <evan@coeus-group.com> --- This seems to also happen on s390x with -mzvector: # s390x-linux-gnu-gcc-10 -march=z14 -mzvector -o test test.c test.c:4:1: internal compiler error: in _cpp_pop_context, at libcpp/macro.c:2644 4 | b(vector double) | ^ 0x11da337 _cpp_pop_context ../../src/libcpp/macro.c:2644 0x11dcd67 expand_arg ../../src/libcpp/macro.c:2601 0x11dc41f replace_args ../../src/libcpp/macro.c:1879 0x11dc41f enter_macro_context ../../src/libcpp/macro.c:1421 0x11dc7e8 cpp_get_token_1 ../../src/libcpp/macro.c:2891 0x6393fe c_lex_with_flags(tree_node**, unsigned int*, unsigned char*, int) ../../src/gcc/c-family/c-lex.c:458 0x5c96a5 c_lex_one_token ../../src/gcc/c/c-parser.c:270 0x5f6517 c_parser_peek_token(c_parser*) ../../src/gcc/c/c-parser.c:474 0x5f6517 c_parse_file() ../../src/gcc/c/c-parser.c:21742 0x64054b c_common_parse_file() ../../src/gcc/c-family/c-opts.c:1190 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <file:///usr/share/doc/gcc-10/README.Bugs> for instructions.
next prev parent reply other threads:[~2021-05-25 1:28 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-20 6:26 [Bug preprocessor/95782] New: " evan@coeus-group.com 2021-05-25 1:28 ` evan@coeus-group.com [this message] 2024-03-26 6:58 ` [Bug target/95782] [s390] " pinskia at gcc dot gnu.org 2024-03-26 6:58 ` pinskia at gcc dot gnu.org 2024-03-27 6:11 ` guojiufu at gcc dot gnu.org 2024-04-28 3:39 ` cvs-commit 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-95782-4-JoBRmkyanW@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).