public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: c++/5565: g++ crashes on struct that is defined twice
@ 2002-04-09 7:26 Jason Merrill
0 siblings, 0 replies; 4+ messages in thread
From: Jason Merrill @ 2002-04-09 7:26 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR c++/5565; it has been noted by GNATS.
From: Jason Merrill <jason@redhat.com>
To: Reichelt <reichelt@igpm.rwth-aachen.de>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c++/5565: g++ crashes on struct that is defined twice
Date: Tue, 09 Apr 2002 15:16:37 +0100
>>>>> "Reichelt" == Reichelt <reichelt@igpm.rwth-aachen.de> writes:
> I agree with you, that the PR should be "high priority" any more.
> However, I find your explanation quite misleading. IMHO "fixed in 3.1"
> would have been more accurate, since it doesn't produce an ICE anymore,
> but only "confused by earlier errors, bailing out" with recent
> snapshots.
The "confused" message is just what a release-branch compiler prints if
there's an ICE after there have already been valid error messages.
Development compilers always give the ICE message. No bug was fixed; only
the output has been changed.
Jason
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: c++/5565: g++ crashes on struct that is defined twice
@ 2002-11-05 7:39 reichelt
0 siblings, 0 replies; 4+ messages in thread
From: reichelt @ 2002-11-05 7:39 UTC (permalink / raw)
To: gcc-bugs, gcc-prs, nobody, reichelt
Synopsis: g++ crashes on struct that is defined twice
State-Changed-From-To: analyzed->closed
State-Changed-By: reichelt
State-Changed-When: Tue Nov 5 07:39:14 2002
State-Changed-Why:
Fixed on mainline.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5565
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: c++/5565: g++ crashes on struct that is defined twice
@ 2002-04-08 17:12 jason
0 siblings, 0 replies; 4+ messages in thread
From: jason @ 2002-04-08 17:12 UTC (permalink / raw)
To: gcc-bugs, gcc-prs, nobody, reichelt
Synopsis: g++ crashes on struct that is defined twice
State-Changed-From-To: open->analyzed
State-Changed-By: jason
State-Changed-When: Mon Apr 8 17:12:25 2002
State-Changed-Why:
This is not a regression. 2.95 also crashes on this testcase.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5565
^ permalink raw reply [flat|nested] 4+ messages in thread
* c++/5565: g++ crashes on struct that is defined twice
@ 2002-02-01 1:46 reichelt
0 siblings, 0 replies; 4+ messages in thread
From: reichelt @ 2002-02-01 1:46 UTC (permalink / raw)
To: gcc-gnats
>Number: 5565
>Category: c++
>Synopsis: g++ crashes on struct that is defined twice
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: ice-on-illegal-code
>Submitter-Id: net
>Arrival-Date: Fri Feb 01 01:46:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: Volker Reichelt
>Release: gcc 3.1 20020128 (experimental)
>Organization:
>Environment:
i686-pc-linux-gnu, mips-sgi-irix6.5
>Description:
g++ crashes on the following code
struct Base { virtual void f(); };
struct Wrong : public Base {};
struct Wrong : public Base {};
with the error message
bug.cpp:3: redefinition of `struct Wrong'
bug.cpp:2: previous definition of `struct Wrong'
bug.cpp:3: Internal compiler error in build_primary_vtable, at
cp/class.c:638
Please submit a full bug report, [etc.]
Just compile the code with "g++ -c".
The same code caused different problems with gcc 2.96,
see PR 1519.
>How-To-Repeat:
g++ -c filename.cpp
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2002-11-05 15:39 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-04-09 7:26 c++/5565: g++ crashes on struct that is defined twice Jason Merrill
-- strict thread matches above, loose matches on Subject: below --
2002-11-05 7:39 reichelt
2002-04-08 17:12 jason
2002-02-01 1:46 reichelt
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).