public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: reichelt@igpm.rwth-aachen.de
To: gcc-gnats@gcc.gnu.org
Subject: c++/5921: ICE with static variable
Date: Tue, 12 Mar 2002 06:06:00 -0000 [thread overview]
Message-ID: <20020312135640.8915.qmail@sources.redhat.com> (raw)
>Number: 5921
>Category: c++
>Synopsis: ICE with static variable
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: ice-on-illegal-code
>Submitter-Id: net
>Arrival-Date: Tue Mar 12 06:06:03 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: Volker Reichelt
>Release: gcc version 3.1 20020304 (prerelease)
>Organization:
>Environment:
mips-sgi-irix6.5, i686-pc-linux-gnu
>Description:
The following code snippet causes an ICE when compiled
with gcc 3.1. It's a regression vs. gcc 3.0.x.
----------------------snip here------------------
struct A
{
struct B { B(); };
};
static A::B b;
inline template <int i> void f ();
----------------------snip here------------------
The error message is:
bug.cpp:8: parse error before `<' token
bug.cpp:6: definition provided for explicit instantiation
bug.cpp:6: non-template used as template
bug.cpp:6: internal error: Segmentation fault
Please submit a full bug report, [etc.]
The example above is very similar to PR 5624. It looks
as if both show different symptoms of the same bug.
Maybe the patch for PR 5624 that cured one symptom
gets superfluous, once the underlying real bug is fixed.
Therefore, IMHO, PR 5624 should be revisited, too.
Since a similar static declaration occurs in iostream
(A == ios_base and B == Init), the bug might affect
quite a number of programs.
>How-To-Repeat:
g++ -c bug.cpp
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-03-12 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-12 6:06 reichelt [this message]
2002-04-06 22:15 mmitchel
2002-12-30 14:36 Volker Reichelt
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=20020312135640.8915.qmail@sources.redhat.com \
--to=reichelt@igpm.rwth-aachen.de \
--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).