public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/11770] segv
Date: Tue, 05 Aug 2003 19:44:00 -0000	[thread overview]
Message-ID: <20030805194403.23145.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030802074217.11770.igodard@pacbell.net>

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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


bangerth at dealii dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED


------- Additional Comments From bangerth at dealii dot org  2003-08-05 19:44 -------
Confirmed. Here's a reduced testcase:
------------------------------
template<typename T>
struct B {
    typedef B<T> S;
};

template<typename T>
struct D : B<T> {
    friend class S;
    D(T v) : B(v) {}
};
------------------------------------
This ICEs every gcc version up to and including 3.3:
g/x> /home/bangerth/bin/gcc-3.3-pre/bin/c++ -c x.cc
x.cc:8: warning: `class S' declares a new type at namespace scope
x.cc:8: warning:   names from dependent base classes are not visible to
   unqualified name lookup - to refer to the inherited type, say `class D::S'
x.cc:9: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.

However, this seems already fixed in mainline.

W.


      parent reply	other threads:[~2003-08-05 19:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-02  7:42 [Bug c++/11770] New: segv igodard at pacbell dot net
2003-08-02  7:44 ` [Bug c++/11770] segv igodard at pacbell dot net
2003-08-02  7:44 ` igodard at pacbell dot net
2003-08-02 15:33 ` pinskia at physics dot uc dot edu
2003-08-05 19:44 ` bangerth at dealii dot org [this message]

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=20030805194403.23145.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).