public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Pop Sébastian" <pop@gauvain.u-strasbg.fr>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/8134: ICE in force_store_init_value on legal code
Date: Tue, 08 Oct 2002 14:36:00 -0000 [thread overview]
Message-ID: <20021008213601.21842.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/8134; it has been noted by GNATS.
From: =?iso-8859-1?Q?Pop_S=E9bastian?= <pop@gauvain.u-strasbg.fr>
To: lerdsuwa@gcc.gnu.org, alvaro@rentec.com, gcc-bugs@gcc.gnu.org,
gcc-prs@gcc.gnu.org, georgeh@rentec.com, nobody@gcc.gnu.org,
gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: c++/8134: ICE in force_store_init_value on legal code
Date: Tue, 8 Oct 2002 23:31:02 +0200
On Fri, Oct 04, 2002 at 03:10:30PM -0000, lerdsuwa@gcc.gnu.org wrote:
> Synopsis: ICE in force_store_init_value on legal code
>
> State-Changed-From-To: open->analyzed
> State-Changed-By: lerdsuwa
> State-Changed-When: Fri Oct 4 08:10:29 2002
> State-Changed-Why:
> Confirmed. Regression from GCC 3.0.
>
> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8134
I can reproduce the bug with
gcc version 3.2.1 20020924 (Debian prerelease)
The bug is not present in:
gcc version 3.0.4
nor in the latest version in CVS:
version gcc 3.3 20021007 (experimental)
Seems like the bug was a duplicate of another bug fixed in the mainline.
I suggest to close this PR.
Sebastian
next reply other threads:[~2002-10-08 21:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-08 14:36 Pop Sébastian [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-16 12:40 mmitchel
2002-10-09 10:56 Pop Sébastian
2002-10-08 15:06 Pop Sébastian
2002-10-08 15:06 Gabriel Dos Reis
2002-10-04 8:10 lerdsuwa
2002-10-03 12:26 georgeh
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=20021008213601.21842.qmail@sources.redhat.com \
--to=pop@gauvain.u-strasbg.fr \
--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).