public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: reichelt@igpm.rwth-aachen.de
To: bmiller@txcorp.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: c++/9589: Segmentation fault on missing semicolon after class definition.
Date: Thu, 06 Feb 2003 23:26:00 -0000	[thread overview]
Message-ID: <20030206232620.18002.qmail@sources.redhat.com> (raw)

Synopsis: Segmentation fault on missing semicolon after class definition.

State-Changed-From-To: open->closed
State-Changed-By: reichelt
State-Changed-When: Thu Feb  6 23:26:19 2003
State-Changed-Why:
    Confirmed, but fixed on 3.3 branch and mainline.
    
    A reduced testcase is the following:
    
    ---------------------snip here----------------------
    struct A
    {
        A();
        void foo() const;
    };
    
    struct B
    {
        void bar (const A &a) const { a.foo(); }
    } // missing semicolon
    
    A::A () {}
    ---------------------snip here----------------------
    
    It crashes gcc 2.95.x, 3.0.x, 3.1.x, 3.2.x.
    However, the code gives a regular error with 3.3 branch and mainline.
    Since it's not a regression I close the PR.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9589


             reply	other threads:[~2003-02-06 23:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-06 23:26 reichelt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-05 19:46 bmiller

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=20030206232620.18002.qmail@sources.redhat.com \
    --to=reichelt@igpm.rwth-aachen.de \
    --cc=bmiller@txcorp.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).