public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: e97_far@e.kth.se, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: c++/10259: segmentation fault
Date: Sat, 29 Mar 2003 00:32:00 -0000	[thread overview]
Message-ID: <20030329000725.11584.qmail@sources.redhat.com> (raw)

Synopsis: segmentation fault

State-Changed-From-To: feedback->closed
State-Changed-By: bangerth
State-Changed-When: Sat Mar 29 00:07:24 2003
State-Changed-Why:
    Actually, there was enough information in the PR. This is
    an extract:
    ----------------------
    struct X { X();                };
    struct B { static void foo (); };
    
    struct Y {
        void foo() {
          B::foo();
        }
    }
    
    X::X() {}
    -----------------------
    Note the missing semicolon after the declaration of struct
    Y! With 3.2.3, we get this:
    g/x> /home/bangerth/bin/gcc-3.2.3-pre/bin/c++ -c y.cc
    y.cc:10: internal error: Segmentation fault
    
    This ICEd with 2.95 and 3.0 as well, so is not a regression.
    On the other hand, 3.3 and 3.4 are fixed:
    
    g/x> /home/bangerth/bin/gcc-3.3-pre/bin/c++ -c y.cc
    y.cc:10: error: ISO C++ forbids defining types within return type
    y.cc:10: error: `void ()()' is not an aggregate type
    y.cc:10: error: semicolon missing after declaration of `struct Y'
    g/x>
    g/x> /home/bangerth/bin/gcc-3.4-pre/bin/c++ -c y.cc
    y.cc:10: error: return type specification for constructor invalid
    
    Since this is not a regression, the bug will certainly
    not be fixed for 3.2.3, so I close this report.
    
    W.

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


             reply	other threads:[~2003-03-29  0:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-29  0:32 bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-29  0:07 ebotcazou
2003-03-28 23:01 e97_far

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=20030329000725.11584.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=e97_far@e.kth.se \
    --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).