public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: conversy@emn.fr
To: gcc-gnats@gcc.gnu.org
Subject: c++/3084: anonymous namespace linking
Date: Fri, 08 Jun 2001 04:56:00 -0000	[thread overview]
Message-ID: <20010608114905.11866.qmail@sourceware.cygnus.com> (raw)

>Number:         3084
>Category:       c++
>Synopsis:       anonymous namespace linking
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          wrong-code
>Submitter-Id:   net
>Arrival-Date:   Fri Jun 08 04:56:02 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     conversy@emn.fr
>Release:        gcc version 3.0 20010426 (Debian prerelease)
>Organization:
>Environment:
i386-linux
>Description:
anonymous namespace functions cannot be linked
to global call to these functions.

There is an error when linking an object file with
the code of a function declared inside a unnamed
"namespace {}".

In the .o that includes the function code, the name
is the form *__GLOBAL__* where in the .o that refers
to the function code, the name is different.


>How-To-Repeat:
g++ AB.cpp test.cpp

gives: undefined reference to `(anonymous namespace)::operator<<(std::ostream&, (anonymous namespace)::A const&)'


AB.h:

namespace std {
  struct ostream {};
  extern ostream cout;
};

namespace {
  struct A {};
  std::ostream& operator<<(std::ostream&, const A&);
}

namespace foo {
  struct B {};
}

std::ostream& operator<<(std::ostream&, const foo::B&);

AB.cpp:
#include "AB.h"

namespace {
  std::ostream& operator<<(std::ostream& out, const A&) { return out; }
}

std::ostream& operator<<(std::ostream& out, const foo::B&) { return out; }

test.cpp:
#include "AB.h"

main()
{
  A a;
  std::cout << a;
  foo::B b;
  std::cout << b;
}




>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-06-08  4:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-08  4:56 conversy [this message]
2001-06-08  6:26 Artem Khodush
2001-07-11 10:44 mmitchel

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=20010608114905.11866.qmail@sourceware.cygnus.com \
    --to=conversy@emn.fr \
    --cc=gcc-gnats@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).