From: Neal Becker <neal@ctd.comsat.com>
To: egcs@cygnus.com
Subject: 970907 hpux9.05 failures
Date: Mon, 08 Sep 1997 12:27:00 -0000 [thread overview]
Message-ID: <E0x89Se-00012C-00@data.ctd.comsat.com> (raw)
egcs-970907 hpux9.05 hppa1.1
FAIL: gcc.c-torture/compile/961203-1.c, -O0
FAIL: gcc.c-torture/compile/961203-1.c, -O1
FAIL: gcc.c-torture/compile/961203-1.c, -O2
FAIL: gcc.c-torture/compile/961203-1.c, -O2 -fomit-frame-pointer -finline-functions
...
FAIL: gcc.c-torture/execute/ieee/fp-cmp-1.c execution, -O0
Executing on host: /src/egcs-970907/gcc/xgcc -B/src/egcs-970907/gcc/ /src/egcs-970907/gcc/testsuite/gcc.c-torture/compile/961203-1.c -w -O0 -c -o /tmp/961203-1.o
compiler exited with status 1
output is:
xgcc: Internal compiler error: program cc1 got fatal signal 10
FAIL: gcc.c-torture/compile/961203-1.c, -O0
Executing on host: /src/egcs-970907/gcc/xgcc -B/src/egcs-970907/gcc/ /src/egcs-970907/gcc/testsuite/gcc.c-torture/compile/961203-1.c -w -O1 -c -o /tmp/961203-1.o
compiler exited with status 1
output is:
xgcc: Internal compiler error: program cc1 got fatal signal 10
Executing on host: /src/egcs-970907/gcc/xgcc -B/src/egcs-970907/gcc/ /src/egcs-970907/gcc/testsuite/gcc.c-torture/compile/961203-1.c -w -O2 -c -o /tmp/961203-1.o
compiler exited with status 1
output is:
xgcc: Internal compiler error: program cc1 got fatal signal 10
FAIL: gcc.c-torture/compile/961203-1.c, -O2
Executing on host: /src/egcs-970907/gcc/xgcc -B/src/egcs-970907/gcc/ /src/egcs-970907/gcc/testsuite/gcc.c-torture/compile/961203-1.c -w -O2 -fomit-frame-pointer -finline-functions -c -o /tmp/961203-1.o
compiler exited with status 1
output is:
xgcc: Internal compiler error: program cc1 got fatal signal 10
FAIL: gcc.c-torture/compile/961203-1.c, -O2 -fomit-frame-pointer -finline-functions
next reply other threads:[~1997-09-08 12:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-08 12:27 Neal Becker [this message]
1997-09-08 14:08 ` Jeffrey A Law
1997-09-09 6:50 ` Neal Becker
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=E0x89Se-00012C-00@data.ctd.comsat.com \
--to=neal@ctd.comsat.com \
--cc=egcs@cygnus.com \
/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).