public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/107080] New: ICE in verify_symtab_nodes using _Float64x with long double Date: Thu, 29 Sep 2022 00:09:41 +0000 [thread overview] Message-ID: <bug-107080-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107080 Bug ID: 107080 Summary: ICE in verify_symtab_nodes using _Float64x with long double Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: jsm28 at gcc dot gnu.org CC: jakub at gcc dot gnu.org Target Milestone: --- Target: x86_64-* i?86-* ia64-* Compiling the following C++ test for x86_64 (or i686 or ia64) produces an ICE, no optimization or other options required (presumably introduced by the _FloatN / _FloatNx support for C++). template<typename> struct S; template<> struct S<long double> { static int call (long double x, long double y) throw () { return 3; } }; template<> struct S<_Float64x> { static int call (_Float64x x, _Float64x y) throw () { return 3; } }; template<typename T1, typename T2> inline int g (T1 x, T2 y) throw () { typedef decltype (x + y) T3; return S<T3>::call (x, y); } int f () { return g (0.0f64x, 0.0f64x) + g (0.0f64x, 0.0L); } t.cc:31:1: error: Two symbols with same comdat_group are not linked by the same_comdat_group list. 31 | } | ^ _Z1gIeeEiT_T0_/4 (int g(T1, T2) [with T1 = _Float64x; T2 = long double]) Type: function definition analyzed Visibility: semantic_interposition no_reorder public weak comdat comdat_group:_Z1gIeeEiT_T0_ one_only previous sharing asm name: 3 References: __gxx_personality_v0/5 (addr) Referring: Function flags: body Called by: _Z1fv/2 Calls: _ZN1SIeE4callEee/1 _Z1gIeeEiT_T0_/3 (int g(T1, T2) [with T1 = _Float64x; T2 = _Float64x]) Type: function definition analyzed Visibility: semantic_interposition no_reorder public weak comdat comdat_group:_Z1gIeeEiT_T0_ one_only next sharing asm name: 4 References: __gxx_personality_v0/5 (addr) Referring: Function flags: body Called by: _Z1fv/2 Calls: _ZN1SIeE4callEee/1 t.cc:31:1: internal compiler error: symtab_node::verify failed 0xc9ba69 symtab_node::verify_symtab_nodes() /scratch/jmyers/glibc/many13/src/gcc/gcc/symtab.cc:1410 0xcb4ab3 symtab_node::checking_verify_symtab_nodes() /scratch/jmyers/glibc/many13/src/gcc/gcc/cgraph.h:682 0xcb4ab3 symbol_table::compile() /scratch/jmyers/glibc/many13/src/gcc/gcc/cgraphunit.cc:2264 0xcb80cd symbol_table::compile() /scratch/jmyers/glibc/many13/src/gcc/gcc/cgraphunit.cc:2261 0xcb80cd symbol_table::finalize_compilation_unit() /scratch/jmyers/glibc/many13/src/gcc/gcc/cgraphunit.cc:2529 Please submit a full bug report, with preprocessed source (by using -freport-bug). Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions.
next reply other threads:[~2022-09-29 0:09 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-29 0:09 jsm28 at gcc dot gnu.org [this message] 2022-09-29 2:31 ` [Bug c++/107080] " pinskia at gcc dot gnu.org 2022-09-29 11:41 ` jakub at gcc dot gnu.org 2022-09-30 16:41 ` cvs-commit at gcc dot gnu.org 2022-09-30 16:43 ` jakub at gcc dot gnu.org 2022-09-30 17:53 ` cvs-commit at gcc dot gnu.org 2022-09-30 19:55 ` 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-107080-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).