public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-52094-4-ZKRg9TIFRE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52094-4@http.gcc.gnu.org/bugzilla/>

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.


  parent reply	other threads:[~2013-09-29 19:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-02  9:59 [Bug c++/52094] New: g++ yields different behaviour for postfix increment and decrement operators with fundamental types vs. classes dicomj23 at gmail dot com
2012-02-02 10:04 ` [Bug c++/52094] internal compiler error: Segmentation fault (program cc1plus) dicomj23 at gmail dot com
2012-02-02 10:23 ` [Bug c++/52094] ICE on definition of nested class in wrong namespace scope with wrong nested-name-qualifier redi at gcc dot gnu.org
2012-02-02 10:26 ` redi at gcc dot gnu.org
2012-02-02 10:34 ` dicomj23 at gmail dot com
2012-02-02 10:43 ` redi at gcc dot gnu.org
2013-09-29 19:15 ` arnaut.billings at yahoo dot com [this message]
2020-07-23 14:39 ` mpolacek at gcc dot gnu.org
2021-08-04 19:48 ` pinskia at gcc dot gnu.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-52094-4-ZKRg9TIFRE@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).