From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-430762-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 28901 invoked by alias); 29 Sep 2013 19:15:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Received: (qmail 28649 invoked by uid 48); 29 Sep 2013 19:15:04 -0000
From: "arnaut.billings at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/52094] ICE on definition of nested class in wrong namespace scope with wrong nested-name-qualifier
Date: Sun, 29 Sep 2013 19:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.6.1
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: arnaut.billings at yahoo dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-52094-4-ZKRg9TIFRE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-52094-4@http.gcc.gnu.org/bugzilla/>
References: <bug-52094-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2013-09/txt/msg02002.txt.bz2

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

arnaut.billings at yahoo dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |arnaut.billings at yahoo dot com

--- Comment #6 from arnaut.billings at yahoo dot com ---
Cygwin gcc (GCC) 4.7.3

Nested class in wrong class with typedef name qualifier also causes a
segmentation fault:

struct Foo
{
  struct Impl;
};

struct Bar
{
  typedef Foo base_type;

  struct base_type::Impl
  {
  };

};

Note: if "struct base_type::Impl" is changed to "struct Foo::Impl" then it will
produce an error message.