public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "haoxintu at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/96162] New: [11 Regression] ICE in discriminator_for_local_entity, at cp/mangle.c:1910 Date: Sat, 11 Jul 2020 05:58:16 +0000 [thread overview] Message-ID: <bug-96162-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96162 Bug ID: 96162 Summary: [11 Regression] ICE in discriminator_for_local_entity, at cp/mangle.c:1910 Product: gcc Version: 11.0 Status: UNCONFIRMED Keywords: error-recovery, ice-on-invalid-code Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: haoxintu at gmail dot com Target Milestone: --- Hi, all. This code, test.cc, is an invalid code, makes GCC-trunk ICE. Interestingly, this code does not trigger other released GCC-10 or GCC-9 ICE (confused by earlier errors, bailing out). I guess this is a special regression error-recovery case that is different from others. $cat test.cc #include <iostream> void foo() { for (thread_local int * a ){} } $g++ test.cc test.cc: In function ‘void foo()’: test.cc:3:30: error: expected ‘;’ before ‘)’ token 3 | for (thread_local int * a ){} | ^~ | ; test.cc:3:31: error: expected primary-expression before ‘)’ token 3 | for (thread_local int * a ){} | ^ test.cc:3:30: error: expected ‘;’ before ‘)’ token 3 | for (thread_local int * a ){} | ^~ | ; test.cc: At global scope: test.cc:3:29: internal compiler error: in discriminator_for_local_entity, at cp/mangle.c:1910 3 | for (thread_local int * a ){} | ^ 0x69e943 discriminator_for_local_entity ../../gcc/cp/mangle.c:1910 0x9cdee8 write_local_name ../../gcc/cp/mangle.c:2019 0x9cdee8 write_name ../../gcc/cp/mangle.c:973 0x9d05a7 write_encoding ../../gcc/cp/mangle.c:825 0x9d5981 mangle_decl_string ../../gcc/cp/mangle.c:3858 0x9d5ba6 get_mangled_id ../../gcc/cp/mangle.c:3879 0x9d5ba6 mangle_decl(tree_node*) ../../gcc/cp/mangle.c:3917 0x12fca7d decl_assembler_name(tree_node*) ../../gcc/tree.c:708 0xbf17d9 symbol_table::insert_to_assembler_name_hash(symtab_node*, bool) ../../gcc/symtab.c:174 0xbf193c symbol_table::symtab_initialize_asm_name_hash() ../../gcc/symtab.c:266 0xbf2334 symbol_table::symtab_initialize_asm_name_hash() ../../gcc/symtab.c:1033 0xbf2334 symtab_node::get_for_asmname(tree_node const*) ../../gcc/symtab.c:1021 0xc02e60 handle_alias_pairs ../../gcc/cgraphunit.c:1512 0xc08ccc symbol_table::finalize_compilation_unit() ../../gcc/cgraphunit.c:2962 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. $g++ -v Using built-in specs. COLLECT_GCC=g++ COLLECT_LTO_WRAPPER=/home/haoxin/compilers/gcc/build/libexec/gcc/x86_64-pc-linux-gnu/11.0.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: ../configure CC=gcc-10 CXX=g++-10 --prefix=/home/haoxin/compilers/gcc/build/ --enable-languages=c,c++ --disable-multilib Thread model: posix Supported LTO compression algorithms: zlib gcc version 11.0.0 20200708 (experimental) (GCC) Thanks, Haoxin
next reply other threads:[~2020-07-11 5:58 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-11 5:58 haoxintu at gmail dot com [this message] 2020-07-13 7:58 ` [Bug c++/96162] " rguenth at gcc dot gnu.org 2020-07-14 14:19 ` haoxintu at gmail dot com 2020-10-16 11:58 ` rguenth at gcc dot gnu.org 2021-04-27 11:39 ` [Bug c++/96162] [11/12 " jakub at gcc dot gnu.org 2021-07-28 7:04 ` rguenth at gcc dot gnu.org 2021-09-10 23:44 ` pinskia at gcc dot gnu.org 2021-09-10 23:50 ` [Bug c++/96162] [9/10/11/12 " pinskia at gcc dot gnu.org 2021-09-10 23:50 ` pinskia at gcc dot gnu.org 2022-05-27 9:43 ` [Bug c++/96162] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:41 ` jakub at gcc dot gnu.org 2023-07-07 10:37 ` [Bug c++/96162] [11/12/13/14 " rguenth 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-96162-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).