public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/33486] namespace association doesn't handle parallel namespaces
Date: Mon, 25 Feb 2008 02:04:00 -0000	[thread overview]
Message-ID: <20080225020342.22908.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33486-102@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from jason at gcc dot gnu dot org  2008-02-25 02:03 -------
This is a compiler bug.


-- 

jason at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|bkoz at gcc dot gnu dot org |jason at gcc dot gnu dot org
          Component|libstdc++                   |c++
            Summary|parallel v3: functions not  |namespace association
                   |in right namespace          |doesn't handle parallel
                   |                            |namespaces


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


  parent reply	other threads:[~2008-02-25  2:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-19  2:34 [Bug libstdc++/33486] New: parallel v3: functions not in right namespace bangerth at dealii dot org
2007-09-19 17:05 ` [Bug libstdc++/33486] " bkoz at gcc dot gnu dot org
2007-10-10  1:07 ` bangerth at dealii dot org
2008-01-21 15:23 ` singler at gcc dot gnu dot org
2008-01-21 22:12 ` bangerth at dealii dot org
2008-02-25  2:04 ` jason at gcc dot gnu dot org [this message]
2008-02-25  6:27 ` [Bug c++/33486] namespace association doesn't handle parallel namespaces jason at gcc dot gnu dot org
2008-04-01 19:34 ` bkoz at gcc dot gnu dot org
2008-04-07 17:29 ` jason at redhat dot com
2008-04-11 17:32 ` bkoz at gcc dot gnu dot org
2008-04-18 19:58 ` jason at gcc dot gnu dot org
2008-04-23 16:41 ` bkoz 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=20080225020342.22908.qmail@sourceware.org \
    --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).