public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/26155]  New: ICE after error with namespace alias
Date: Tue, 07 Feb 2006 14:48:00 -0000	[thread overview]
Message-ID: <bug-26155-6528@http.gcc.gnu.org/bugzilla/> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 926 bytes --]

I thought this was filed before but I cannot find it.
Testcase:
namespace std
{
  namespace __gnu_debug {
namespace debug = std::__gnu_debug;
namespace debug
{
-----
Error we get:
t.ii:6: error: namespace alias ‘std::__gnu_debug::debug’ not allowed here,
assuming ‘std::__gnu_debug’
t.ii:6: internal compiler error: in resume_scope, at cp/name-lookup.c:1372
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.


-- 
           Summary: ICE after error with namespace alias
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Keywords: ice-on-invalid-code, error-recovery
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: pinskia at gcc dot gnu dot org


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


             reply	other threads:[~2006-02-07 14:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-07 14:48 pinskia at gcc dot gnu dot org [this message]
2006-02-08 21:40 ` [Bug c++/26155] " bkoz at gcc dot gnu dot org
2006-02-09  0:41 ` pinskia at gcc dot gnu dot org
2006-02-09 16:51 ` reichelt at gcc dot gnu dot org
2009-03-24 10:40 ` doko at ubuntu dot com
2009-12-29 16:49 ` debian-gcc at lists dot debian 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-26155-6528@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).