public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/18701] New: [4.0 regression] mmix-knuth-mmixware gcc.c-torture/execute failures: 20010224-1.c, 20020216-1.c, 20040218-1.c, 20040709-2.c
Date: Sun, 28 Nov 2004 14:40:00 -0000 [thread overview]
Message-ID: <20041128144007.18701.hp@gcc.gnu.org> (raw)
With LAST_UPDATED: "Sun Nov 28 09:51:57 UTC 2004" I get:
FAIL: gcc.c-torture/execute/20010224-1.c execution, -O3 -fomit-frame-pointer
-funroll-loops
FAIL: gcc.c-torture/execute/20010224-1.c execution, -O3 -fomit-frame-pointer
-funroll-all-loops -finline-functions
FAIL: gcc.c-torture/execute/20020216-1.c execution, -O1
FAIL: gcc.c-torture/execute/20020216-1.c execution, -O2
FAIL: gcc.c-torture/execute/20020216-1.c execution, -O3 -fomit-frame-pointer
FAIL: gcc.c-torture/execute/20020216-1.c execution, -O3 -g
FAIL: gcc.c-torture/execute/20020216-1.c execution, -Os
FAIL: gcc.c-torture/execute/20040218-1.c execution, -O1
FAIL: gcc.c-torture/execute/20040218-1.c execution, -O2
FAIL: gcc.c-torture/execute/20040218-1.c execution, -O3 -fomit-frame-pointer
FAIL: gcc.c-torture/execute/20040218-1.c execution, -O3 -g
FAIL: gcc.c-torture/execute/20040218-1.c execution, -Os
FAIL: gcc.c-torture/execute/20040709-2.c execution, -Os
With the message in the .log for all being:
*** EXIT code 4242
(a call to abort)
Note that reporting these as one is not a presumption that
these regressions are all due to the same cause, though I will
split this PR only if I later find that's not the case. The
specific number of MMIX regressions didn't seem to be of general
help, so I'm not doing that extra work anymore, I'm just
logging regressions.
Last known to work on: "Tue Nov 23 17:37:12 UTC 2004".
Known to fail on: "Thu Nov 25 02:57:33 UTC 2004"
with patches to fix PR target/18331, where named patches found
not to cause this or any regression on an earlier checkout.
--
Summary: [4.0 regression] mmix-knuth-mmixware gcc.c-
torture/execute failures: 20010224-1.c, 20020216-1.c,
20040218-1.c, 20040709-2.c
Product: gcc
Version: 4.0.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: target
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: hp at gcc dot gnu dot org
CC: gcc-bugs at gcc dot gnu dot org
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: mmix-knuth-mmixware
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18701
next reply other threads:[~2004-11-28 14:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-28 14:40 hp at gcc dot gnu dot org [this message]
2004-11-28 15:08 ` [Bug target/18701] " pinskia at gcc dot gnu dot org
2004-12-02 12:17 ` lerdsuwa at gcc dot gnu dot org
2004-12-19 18:02 ` hp at gcc dot gnu dot org
2004-12-20 0:55 ` steven at gcc dot gnu dot org
2004-12-20 0:59 ` hp at gcc dot gnu dot org
2004-12-20 0:59 ` hp at gcc dot gnu dot org
2004-12-20 1:00 ` hp at bitrange dot com
2004-12-20 1:55 ` hp at gcc dot gnu dot org
2004-12-20 3:40 ` hp at gcc dot gnu dot org
2004-12-23 18:46 ` hp at gcc dot gnu dot org
2004-12-31 16:25 ` cvs-commit at gcc dot gnu dot org
2004-12-31 16:28 ` cvs-commit at gcc dot gnu dot org
2004-12-31 16:33 ` hp at gcc dot gnu dot org
2005-01-21 2:14 ` cvs-commit at gcc dot gnu dot org
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=20041128144007.18701.hp@gcc.gnu.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).