public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Sergei Pachkov <spigel@olvs.miee.ru>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/7063: internal compiler error: Internal compiler error in failed_reload, at reload1.c:5047
Date: Mon, 01 Jul 2002 04:46:00 -0000 [thread overview]
Message-ID: <20020701114609.21144.qmail@sources.redhat.com> (raw)
The following reply was made to PR optimization/7063; it has been noted by GNATS.
From: Sergei Pachkov <spigel@olvs.miee.ru>
To: gerald@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
nobody@gcc.gnu.org, spigel@olvs.miee.ru, gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: optimization/7063: internal compiler error: Internal compiler
error in failed_reload, at reload1.c:5047
Date: Mon, 01 Jul 2002 15:44:01 +0400
gerald@gcc.gnu.org wrote:
>Synopsis: internal compiler error: Internal compiler error in failed_reload, at reload1.c:5047
>
>State-Changed-From-To: open->feedback
>State-Changed-By: gerald
>State-Changed-When: Mon Jul 1 01:52:57 2002
>State-Changed-Why:
> I believe this has been fixed by Bernd Schmidt last week:
> http://gcc.gnu.org/ml/gcc/2002-06/msg01211.html
> http://gcc.gnu.org/ml/gcc/2002-06/msg01709.html
> Can you confirm this?
>
Yes
After test this bug with version gcc 20020630 I'm confirm bugfix by
Bernd Schmidt.
I'm try to compile file attached to my report with option "-O2
-march=athlon-xp" and find new ICE(seg fault without detail report ).
>
>http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7063
>
>
>
next reply other threads:[~2002-07-01 11:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-01 4:46 Sergei Pachkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-02 13:49 gerald
2002-07-01 1:53 gerald
2002-06-27 5:46 Reichelt
2002-06-18 5:23 spigel
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=20020701114609.21144.qmail@sources.redhat.com \
--to=spigel@olvs.miee.ru \
--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).