public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/68092] [C++1z] error: Two symbols with same comdat_group are not linked by the same_comdat_group list.
Date: Mon, 26 Oct 2015 06:43:00 -0000	[thread overview]
Message-ID: <bug-68092-4-z84Rgbf4Bk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-68092-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68092

Markus Trippelsdorf <trippels at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2015-10-26
                 CC|                            |trippels at gcc dot gnu.org
            Summary|[possibly concepts] ICE:    |[C++1z] error: Two symbols
                   |symtab_node::verify failed. |with same comdat_group are
                   |Overloaded function by      |not linked by the
                   |concept requires            |same_comdat_group list.
     Ever confirmed|0                           |1

--- Comment #6 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
markus@x4 tmp % cat class.ii
template <int> bool ConceptTest();
template <int N> class A {
  void foo() const requires ConceptTest<N>() {}
  int foo() const {}
};
template class A<3>;

markus@x4 tmp % g++ -c -std=c++1z class.ii
class.ii:6:20: error: Two symbols with same comdat_group are not linked by the
same_comdat_group list.
 template class A<3>;
                    ^
_ZNK1AILi3EE3fooEv/1 (void A<N>::foo() const [with int N = 3]) @0x7f2d92c57170
  Type: function definition analyzed
  Visibility: forced_by_abi public weak comdat_group:_ZNK1AILi3EE3fooEv
one_only
  previous sharing asm name: 0
  References: 
  Referring: 
  First run: 0
  Function flags: body
  Called by: 
  Calls: 
_ZNK1AILi3EE3fooEv/0 (void A<N>::foo() const requires
predicate((ConceptTest<N>)()) [with int N = 3]) @0x7f2d92c57000
  Type: function definition analyzed
  Visibility: forced_by_abi public weak comdat_group:_ZNK1AILi3EE3fooEv
one_only
  next sharing asm name: 1
  References: 
  Referring: 
  First run: 0
  Function flags: body
  Called by: 
  Calls: 
class.ii:6:20: internal compiler error: symtab_node::verify failed


  parent reply	other threads:[~2015-10-26  6:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-26  1:23 [Bug c++/68092] New: [possibly concepts] ICE: symtab_node::verify failed. Overloaded function by concept requires chrisb2244 at gmail dot com
2015-10-26  1:24 ` [Bug c++/68092] " chrisb2244 at gmail dot com
2015-10-26  1:34 ` chrisb2244 at gmail dot com
2015-10-26  1:34 ` chrisb2244 at gmail dot com
2015-10-26  1:34 ` chrisb2244 at gmail dot com
2015-10-26  1:36 ` chrisb2244 at gmail dot com
2015-10-26  6:43 ` trippels at gcc dot gnu.org [this message]
2023-03-08 21:12 ` [Bug c++/68092] [C++1z] error: Two symbols with same comdat_group are not linked by the same_comdat_group list 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-68092-4-z84Rgbf4Bk@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: link
Be 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).