public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sujian.liu at huawei dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/95677] undefined reference to `(anonymous namespace)::xx'
Date: Mon, 15 Jun 2020 08:36:23 +0000	[thread overview]
Message-ID: <bug-95677-4-SUcSlFGgkD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95677-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from liusujian <sujian.liu at huawei dot com> ---
(In reply to Richard Biener from comment #1)
> It's more likely the GENERIC / cgraph output by the C++ frontend is not
> correct
> and works by accident without LTO.  Initial symbol table:
> 
> Initial Symbol table:
> 
> int {anonymous}::xx/3 (int {anonymous}::xx) @0x7f615d2d8180
>   Type: variable
>   Visibility: external
>   References:
>   Referring: _ZN12_GLOBAL__N_13fooEv/0 (write)
>   Availability: not-ready
>   Varpool flags:
> main/2 (int main()) @0x7f615d421168
>   Type: function definition analyzed
>   Visibility: force_output no_reorder public
>   Aux: @0x37a5000
>   References: int {anonymous}::xx/1 (write)
>   Referring:
>   Function flags: body
>   Called by:
>   Calls:
> int {anonymous}::xx/1 (int {anonymous}::xx) @0x7f615d2d8100
>   Type: variable definition analyzed
>   Visibility: force_output no_reorder
>   Aux: @0x7f615d421168
>   References:
>   Referring: main/2 (write)
>   Availability: not-ready
>   Varpool flags: initialized
> _ZN12_GLOBAL__N_13fooEv/0 (void {anonymous}::foo()) @0x7f615d421000
>   Type: function definition analyzed
>   Visibility: force_output no_reorder
>   Aux: @0x7f615d2d8100
>   References: int {anonymous}::xx/3 (write)
>   Referring:
>   Function flags: body
>   Called by:
>   Calls:
> 
> where you can see there are actually two 'xx' objects and the C++ FE
> takes it up to the linker/assembler to resolve them.  But the symtab
> code does not include such "resolving" step.


In other words, C++ is currently unable to deal with this scenario ? Or any
other problems cause the error?

  parent reply	other threads:[~2020-06-15  8:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15  8:00 [Bug lto/95677] New: " sujian.liu at huawei dot com
2020-06-15  8:12 ` [Bug c++/95677] " rguenth at gcc dot gnu.org
2020-06-15  8:36 ` sujian.liu at huawei dot com [this message]
2020-06-15 12:02 ` nathan at gcc dot gnu.org
2020-06-15 12:05 ` rguenth at gcc dot gnu.org
2020-06-15 12:07 ` rguenth at gcc dot gnu.org
2020-06-15 12:28 ` nathan at gcc dot gnu.org
2020-06-18  7:34 ` sujian.liu at huawei dot com
2020-07-15  1:40 ` sujian.liu at huawei dot com
2020-09-16  8:11 ` sujian.liu at huawei dot com
2020-09-23 17:41 ` nathan at gcc dot gnu.org
2020-10-07 14:35 ` nathan 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-95677-4-SUcSlFGgkD@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).