public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Peter van Hoof <vanhoof@cita.utoronto.ca>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/4329: Internal compiler error in reload_cse_simplify_operands, at reload1.c:8355
Date: Mon, 19 Nov 2001 20:21:00 -0000 [thread overview]
Message-ID: <20011123175601.31782.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR optimization/4329; it has been noted by GNATS.
From: Peter van Hoof <vanhoof@cita.utoronto.ca>
To: rodrigc@gcc.gnu.org
Cc: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org,
nobody@gcc.gnu.org, vanhoof@cita.utoronto.ca
Subject: Re: optimization/4329: Internal compiler error in reload_cse_simplify_operands, at reload1.c:8355
Date: Fri, 23 Nov 2001 12:51:36 -0500
The patch in question does not solve bug 4329. With the patch in place, I still
get exactly the same internal compiler error.
rodrigc@gcc.gnu.org wrote:
> Synopsis: Internal compiler error in reload_cse_simplify_operands, at reload1.c:8355
>
> State-Changed-From-To: open->analyzed
> State-Changed-By: rodrigc
> State-Changed-When: Wed Nov 21 20:31:28 2001
> State-Changed-Why:
> Does this patch help?
> http://gcc.gnu.org/ml/gcc-patches/2001-11/msg00698.html
>
>
> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=4329&database=gcc
>
--
Peter van Hoof
Canadian Institute for Theoretical Astrophysics
McLennan Labs, University of Toronto
Home Page: http://www.cita.utoronto.ca/~vanhoof
Tel: +1-416-978-1777
Fax: +1-416-978-3921
next reply other threads:[~2001-11-23 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-19 20:21 Peter van Hoof [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-24 3:06 rodrigc
2001-11-24 3:05 rodrigc
2001-11-17 16:16 rodrigc
2001-11-17 12:06 rodrigc
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=20011123175601.31782.qmail@sourceware.cygnus.com \
--to=vanhoof@cita.utoronto.ca \
--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).