public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bkoz at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/13294] [3.4 Regression] namespace associations vs. specializations
Date: Wed, 14 Apr 2004 07:52:00 -0000	[thread overview]
Message-ID: <20040414040809.20053.qmail@sources.redhat.com> (raw)
In-Reply-To: <20031204043712.13294.bkoz@gcc.gnu.org>


------- Additional Comments From bkoz at redhat dot com  2004-04-14 04:08 -------
Subject: Re:  [3.4 Regression] namespace associations vs.
 specializations


>(It appears to me that this outcome means that standards-conforming programs do
>not follow the C++ ABI in that specializations of types in "std" are mangled
>incorrectly.  That's observable to user programs by using "typeid".  This is
>presumably a bug in our library implementation, but one that's not easy to fix,
>and hopefully not terribly important to anybody.)
>
>Thank you for persevering with this issue; without having gone this far, we
>probably would not have known what the issues were.

I'm wondering if we should punt on this stuff for 3.4.0, and revert to STL in namespace std.

-benjamin


-- 


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


  parent reply	other threads:[~2004-04-14  4:08 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-04  4:37 [Bug c++/13294] New: " bkoz at gcc dot gnu dot org
2003-12-04  8:03 ` [Bug c++/13294] " pinskia at gcc dot gnu dot org
2003-12-17  5:40 ` mmitchel at gcc dot gnu dot org
2004-01-14  3:36 ` [Bug c++/13294] [3.4 Regression] " pinskia at gcc dot gnu dot org
2004-03-09 10:48 ` [Bug c++/13294] [3.4/3.5 " mmitchel at gcc dot gnu dot org
2004-03-25 22:12 ` jason at redhat dot com
2004-03-26  6:40   ` Gabriel Dos Reis
2004-03-26  6:41 ` gdr at integrable-solutions dot net
2004-03-26 17:22 ` bkoz at gcc dot gnu dot org
2004-03-26 19:21 ` cvs-commit at gcc dot gnu dot org
2004-03-26 19:35 ` [Bug c++/13294] [3.4 " pinskia at gcc dot gnu dot org
2004-03-30 17:58 ` mmitchel at gcc dot gnu dot org
2004-03-31  2:10 ` cvs-commit at gcc dot gnu dot org
2004-03-31  2:28 ` pinskia at gcc dot gnu dot org
2004-04-05 23:20 ` jason at gcc dot gnu dot org
2004-04-06  4:39 ` jason at gcc dot gnu dot org
2004-04-06  9:01 ` mmitchel at gcc dot gnu dot org
2004-04-07 17:58 ` jason at redhat dot com
2004-04-07 19:18 ` mark at codesourcery dot com
2004-04-08 20:35 ` bkoz at gcc dot gnu dot org
2004-04-08 20:37 ` bkoz at gcc dot gnu dot org
2004-04-08 20:43 ` jason at redhat dot com
2004-04-08 22:46 ` gdr at integrable-solutions dot net
2004-04-08 22:48 ` gdr at integrable-solutions dot net
2004-04-08 22:49 ` gdr at integrable-solutions dot net
2004-04-08 23:04 ` bkoz at gcc dot gnu dot org
2004-04-09  6:37 ` jason at redhat dot com
2004-04-13 18:56 ` jason at redhat dot com
2004-04-13 23:49 ` mmitchel at gcc dot gnu dot org
2004-04-14  7:52 ` bkoz at redhat dot com [this message]
2004-04-14 11:36 ` giovannibajo at libero dot it
2004-04-14 14:39 ` bangerth at dealii dot org
2004-04-14 19:04 ` gdr at integrable-solutions dot net
2004-04-14 19:45 ` jason at redhat dot com
2004-04-14 19:48 ` cvs-commit at gcc dot gnu dot org
2004-04-14 21:21 ` cvs-commit at gcc dot gnu dot org
2004-04-14 21:21 ` jason at gcc dot gnu dot org
2004-04-16 18:51 ` mark at codesourcery dot com
2004-04-16 19:41 ` bkoz at redhat dot com
2004-04-17  2:51 ` mark at codesourcery dot com

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=20040414040809.20053.qmail@sources.redhat.com \
    --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).