From: Jeffrey A Law <law@cygnus.com>
To: Craig Burley <burley@gnu.org>
Cc: schmid@ltoi.iap.physik.tu-darmstadt.de, egcs@cygnus.com
Subject: Re: results for egcs-2.91.26 586-pc-linux-gnulibc1
Date: Tue, 05 May 1998 23:29:00 -0000 [thread overview]
Message-ID: <5682.894425094@hurl.cygnus.com> (raw)
In-Reply-To: <199805051634.MAA09904@melange.gnu.org>
In message < 199805051634.MAA09904@melange.gnu.org >you write:
> >g77.log:FAIL: g77.f-torture/compile/970125-0.f, -O1
> >expr.c:7255: Internal compiler error in function expand_expr
>
> The above is almost certainly a back-end bug, not a g77 bug. (I'm
> not looking into this myself, too busy with straight g77 stuff
> these days.)
That's a safe bet.
> >g77.log:FAIL: g77.f-torture/compile/980424-0.f, -O1
> >reg-stack.c:2397: Internal compiler error in function subst_stack_regs_pat
>
> I've run into this myself, 99.99999% likely to be a back-end bug. (Ditto.)
Likewise.
> >g77.log:FAIL: g77.f-torture/compile/980427-0.f, -O0
> >f/com.c:938: failed assertion `TREE_CODE (TREE_TYPE (e)) == REAL_TYPE'
> >g77: Internal compiler error: program f771 got fatal signal 6
>
> 100% likely g77 bug, and we already have a fix, which will probably
> get installed in egcs within the next few days. (It's a three-liner
> that can be found among the "hot" fixes described for g77 0.5.22 in
> < ftp://alpha.gnu.org/g77.plan >.)
Cool.
An FYI -- these mirror my results on an x86 from a build today...
jeff
prev parent reply other threads:[~1998-05-05 23:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-05-04 11:17 Peter Schmid
1998-05-05 13:11 ` Craig Burley
1998-05-05 23:29 ` Jeffrey A Law [this message]
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=5682.894425094@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=burley@gnu.org \
--cc=egcs@cygnus.com \
--cc=schmid@ltoi.iap.physik.tu-darmstadt.de \
/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).