public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bkoz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/36104] [4.3/4.4/4.5/4.6 Regression] gnu-versioned-namespace is broken
Date: Fri, 28 Jan 2011 10:22:00 -0000	[thread overview]
Message-ID: <bug-36104-4-Sr3HLfpLNn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-36104-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36104

--- Comment #15 from Benjamin Kosnik <bkoz at gcc dot gnu.org> 2011-01-28 09:51:23 UTC ---

Patches 1-3 restore gcc-4.2 behavior. Configure works, the library builds, most
all of the tests pass regression, etc.

Unfortunately, this is still annoyingly wrong on close inspection. Namespaces
nested within std containing definitions will be mis-versioned. Using
versioning + modes fails. 

The inline namespace code, which unfortunately includes most of the macros used
to define namespaces in every libstdc++ header, was done as part of the initial
work for this feature, nee namespace association. Then changes were made,
nesting was made de rigeur, and the original macros were pushed and squeezed
into submission. Yet more modes were added: parallel, profile. 

Yet another level of nesting was added for versioning, overloading the
namespace macros with another condition.

C++0x support starts to partition the std:: namespace into finer bits: chrono,
regex, etc. All of these nested namespaces + current macros are wrong.

Patch 4 fixes these issues, and provides a saner infrastructure for future
debug/profile/parallel work.


  parent reply	other threads:[~2011-01-28  9:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-36104-4@http.gcc.gnu.org/bugzilla/>
2010-11-23 11:46 ` jakub at gcc dot gnu.org
2010-11-23 19:19 ` bkoz at gcc dot gnu.org
2011-01-15  1:03 ` bkoz at gcc dot gnu.org
2011-01-15 11:03 ` jakub at gcc dot gnu.org
2011-01-18 20:06 ` bkoz at gcc dot gnu.org
2011-01-19 20:41 ` bkoz at gcc dot gnu.org
2011-01-20 20:12 ` bkoz at gcc dot gnu.org
2011-01-21  0:59 ` bkoz at gcc dot gnu.org
2011-01-28 10:22 ` bkoz at gcc dot gnu.org [this message]
2011-01-30 23:59 ` bkoz at gcc dot gnu.org
2011-02-02 18:19 ` dnovillo at gcc dot gnu.org
2011-03-25 19:58 ` [Bug libstdc++/36104] [4.3/4.4/4.5/4.6/4.7 " jakub at gcc dot gnu.org
2011-04-04 16:59 ` bkoz at gcc dot gnu.org
2008-05-01 20:53 [Bug libstdc++/36104] New: gnu-versioned-namespace is broken in gcc 4.3.0 vorfeed dot canal at gmail dot com
2010-05-22 18:23 ` [Bug libstdc++/36104] [4.3/4.4/4.5/4.6 Regression] gnu-versioned-namespace is broken rguenth at gcc dot gnu dot 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-36104-4-Sr3HLfpLNn@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).