public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rodrigc@gcc.gnu.org
To: gcc-gnats@gcc.gnu.org
Subject: c++/5576: Segfault on legal C++ code
Date: Fri, 01 Feb 2002 14:36:00 -0000	[thread overview]
Message-ID: <20020201223239.4546.qmail@sources.redhat.com> (raw)


>Number:         5576
>Category:       c++
>Synopsis:       Segfault on legal C++ code
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Fri Feb 01 14:36:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     rodrigc@gcc.gnu.org
>Release:        3.1 20020124 (experimental)
>Organization:
>Environment:
System: Linux dibbler 2.4.7-2 #1 Tue Aug 14 05:20:08 EDT 2001 i586 unknown
Architecture: i586
host: i586-pc-linux-gnu
build: i586-pc-linux-gnu
target: i586-pc-linux-gnu
configured with: ./configure --prefix=/opt2/gcc3.1 --enable-shared --enable-threads --enable-languages=c,c++ --enable-checking : (reconfigured) ./configure --prefix=/opt2/gcc3.1 --enable-shared --enable-threads --enable-languages=c,c++ --enable-checking : (reconfigured)
>Description:
Following causes ICE:
(taken from: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=58061)

struct Base
{
  class AutoReadLock
  {
  };
};
struct Standalone
{
  class AutoLock
  {
  };
  typedef AutoLock AutoReadLock;
};
struct Derived:Base
{
  struct LocalMember:public Standalone
  {
  };
  class AutoReadLock
  {
  };
};
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-02-01 22:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-01 14:36 rodrigc [this message]
2002-02-18 18:55 rodrigc

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=20020201223239.4546.qmail@sources.redhat.com \
    --to=rodrigc@gcc.gnu.org \
    --cc=gcc-gnats@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).