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/100888] New: ICE: symtab_node::verify failed, symtab_node::verify() Date: Wed, 02 Jun 2021 21:32:04 +0000 [thread overview] Message-ID: <bug-100888-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100888 Bug ID: 100888 Summary: ICE: symtab_node::verify failed, symtab_node::verify() 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.2G3KkJkZyC-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 20210602 (experimental) [master revision :5b6bc0f6e:b75978d14fc35981ffd8bf060ee52300db4dae50] (GCC) $ cat mutant.c register __sys_res asm("r10"); r10() {} $ gcc-trunk mutant.c mutant.c:1:10: warning: type defaults to ‘int’ in declaration of ‘__sys_res’ [-Wimplicit-int] 1 | register __sys_res asm("r10"); | ^~~~~~~~~ mutant.c:1:10: warning: call-clobbered register used for global register variable mutant.c:2:1: warning: return type defaults to ‘int’ [-Wimplicit-int] 2 | r10() {} | ^~~ mutant.c:2:1: error: assembler name hash list corrupted *r10/0 (__sys_res) @0x7f5bf87f5000 Type: variable definition analyzed Visibility: force_output no_reorder public References: Referring: Availability: not-ready Varpool flags: mutant.c:2:1: internal compiler error: symtab_node::verify failed 0xa717c9 symtab_node::verify() /tmp/tmp.2G3KkJkZyC-gcc-builder/gcc/gcc/symtab.c:1361 0xa717c9 symtab_node::verify() /tmp/tmp.2G3KkJkZyC-gcc-builder/gcc/gcc/symtab.c:1349 0xa72a27 symtab_node::verify_symtab_nodes() /tmp/tmp.2G3KkJkZyC-gcc-builder/gcc/gcc/symtab.c:1384 0xa88b04 symtab_node::checking_verify_symtab_nodes() /tmp/tmp.2G3KkJkZyC-gcc-builder/gcc/gcc/cgraph.h:678 0xa88b04 symbol_table::compile() /tmp/tmp.2G3KkJkZyC-gcc-builder/gcc/gcc/cgraphunit.c:2272 0xa8b7db symbol_table::compile() /tmp/tmp.2G3KkJkZyC-gcc-builder/gcc/gcc/cgraphunit.c:2269 0xa8b7db symbol_table::finalize_compilation_unit() /tmp/tmp.2G3KkJkZyC-gcc-builder/gcc/gcc/cgraphunit.c:2537 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-06-02 21:32 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-02 21:32 cnsun at uwaterloo dot ca [this message] 2021-06-03 9:33 ` [Bug ipa/100888] " marxin at gcc dot gnu.org 2021-08-13 9:58 ` marxin at gcc dot gnu.org 2021-12-24 10:34 ` 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-100888-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).