------- Additional Comments From hp at gcc dot gnu dot org 2005-04-14 01:16
-------
I see this too, for cris-elf, but for 931004-6.c as well.
I'm going to assume it's the same bug (and relevant in this PR)
for two reasons: due to the failure being at -O3:
FAIL: gcc.c-torture/execute/931004-2.c execution, -O3 -fomit-frame-pointer
-funroll-loops
FAIL: gcc.c-torture/execute/931004-2.c execution, -O3 -fomit-frame-pointer
-funroll-all-loops -finline-functions
FAIL: gcc.c-torture/execute/931004-6.c execution, -O3 -fomit-frame-pointer
-funroll-loops
FAIL: gcc.c-torture/execute/931004-6.c execution, -O3 -fomit-frame-pointer
-funroll-all-loops -finline-functions
(the gcc.log says "program stopped with signal 6." hence an abort call)
and because of the timeframe for the appearance of the failure:
the tests worked with LAST_UPDATED "Fri Apr 8 17:09:07 UTC 2005"
and started failing with "Sat Apr 9 01:52:04 UTC 2005".
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |hp at gcc dot gnu dot org
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
GCC target triplet|hppa64-*-hpux11.* |hppa64-*-hpux11.*, cris-elf
Last reconfirmed|0000-00-00 00:00:00 |2005-04-14 01:16:30
date| |
Summary|[4.1 Regression] gcc.c- |[4.1 Regression] gcc.c-
|torture/execute/931004-2.c |torture/execute/931004-2.c
|execution fails on hppa64- |execution fails on hppa64-
|hpux |hpux and cris-elf
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21007
