public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/45962] New: [4.6 Regression]: many c/c++ failures on cris-elf, in r165236:165242
Date: Mon, 11 Oct 2010 03:26:00 -0000 [thread overview]
Message-ID: <bug-45962-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45962
Summary: [4.6 Regression]: many c/c++ failures on cris-elf, in
r165236:165242
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code, wrong-code
Severity: normal
Priority: P3
Component: rtl-optimization
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: hp@gcc.gnu.org
CC: rth@gcc.gnu.org
Host: x86_64-unknown-linux-gnu
Target: cris-axis-elf
Created attachment 22013
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22013
Preprocessed gcc.dg-struct-layout-1//t001_x.c. Run cc1 -w -quiet
-fpreprocessed t001_x.i
With revision 165236 these tests passed.
>From revision 165242 and on, these tests have failed as follows (cutnpasted,
bad wrapping):
Running
/tmp/hpautotest-gcc1/gcc/gcc/testsuite/gcc.c-torture/execute/execute.exp ...
FAIL: gcc.c-torture/execute/20060420-1.c execution, -O1
FAIL: gcc.c-torture/execute/20060420-1.c execution, -O2
FAIL: gcc.c-torture/execute/20060420-1.c execution, -O3 -fomit-frame-pointer
FAIL: gcc.c-torture/execute/20060420-1.c execution, -O3 -fomit-frame-pointer
-funroll-loops
FAIL: gcc.c-torture/execute/20060420-1.c execution, -O3 -fomit-frame-pointer
-funroll-all-loops -finline-functions
FAIL: gcc.c-torture/execute/20060420-1.c execution, -O3 -g
FAIL: gcc.c-torture/execute/20060420-1.c execution, -Os
FAIL: gcc.c-torture/execute/20060420-1.c execution, -O2 -flto
FAIL: gcc.c-torture/execute/20060420-1.c execution, -O2 -fwhopr
... (non-regressions elided)
FAIL: gcc.c-torture/execute/simd-5.c execution, -O0
... (non-regressions elided)
Running /tmp/hpautotest-gcc1/gcc/gcc/testsuite/gcc.dg/compat/compat.exp ...
FAIL: gcc.dg/compat/vector-1 c_compat_x_tst.o-c_compat_y_tst.o execute
FAIL: gcc.dg/compat/vector-2 c_compat_x_tst.o-c_compat_y_tst.o execute
Running
/tmp/hpautotest-gcc1/gcc/gcc/testsuite/gcc.dg/compat/struct-layout-1.exp ...
FAIL: tmpdir-gcc.dg-struct-layout-1/t001 c_compat_x_tst.o compile, (internal
compiler error)
FAIL: tmpdir-gcc.dg-struct-layout-1/t001 c_compat_y_tst.o compile, (internal
compiler error)
FAIL: tmpdir-gcc.dg-struct-layout-1/t002 c_compat_x_tst.o-c_compat_y_tst.o
execute
FAIL: tmpdir-gcc.dg-struct-layout-1/t003 c_compat_x_tst.o-c_compat_y_tst.o
execute
FAIL: tmpdir-gcc.dg-struct-layout-1/t004 c_compat_x_tst.o-c_compat_y_tst.o
execute
FAIL: tmpdir-gcc.dg-struct-layout-1/t005 c_compat_x_tst.o-c_compat_y_tst.o
execute
FAIL: tmpdir-gcc.dg-struct-layout-1/t006 c_compat_x_tst.o compile, (internal
compiler error)
FAIL: tmpdir-gcc.dg-struct-layout-1/t006 c_compat_y_tst.o compile, (internal
compiler error)
FAIL: tmpdir-gcc.dg-struct-layout-1/t007 c_compat_x_tst.o-c_compat_y_tst.o
execute
FAIL: tmpdir-gcc.dg-struct-layout-1/t008 c_compat_x_tst.o-c_compat_y_tst.o
execute
FAIL: tmpdir-gcc.dg-struct-layout-1/t009 c_compat_x_tst.o-c_compat_y_tst.o
execute
FAIL: tmpdir-gcc.dg-struct-layout-1/t010 c_compat_x_tst.o-c_compat_y_tst.o
execute
FAIL: tmpdir-gcc.dg-struct-layout-1/t011 c_compat_x_tst.o-c_compat_y_tst.o
execute
FAIL: tmpdir-gcc.dg-struct-layout-1/t012 c_compat_x_tst.o-c_compat_y_tst.o
execute
FAIL: tmpdir-gcc.dg-struct-layout-1/t013 c_compat_x_tst.o-c_compat_y_tst.o
execute
FAIL: tmpdir-gcc.dg-struct-layout-1/t014 c_compat_x_tst.o-c_compat_y_tst.o
execute
FAIL: tmpdir-gcc.dg-struct-layout-1/t015 c_compat_x_tst.o-c_compat_y_tst.o
execute
FAIL: tmpdir-gcc.dg-struct-layout-1/t016 c_compat_x_tst.o-c_compat_y_tst.o
execute
FAIL: tmpdir-gcc.dg-struct-layout-1/t017 c_compat_x_tst.o-c_compat_y_tst.o
execute
FAIL: tmpdir-gcc.dg-struct-layout-1/t018 c_compat_x_tst.o-c_compat_y_tst.o
execute
FAIL: tmpdir-gcc.dg-struct-layout-1/t019 c_compat_x_tst.o-c_compat_y_tst.o
execute
FAIL: tmpdir-gcc.dg-struct-layout-1/t020 c_compat_x_tst.o-c_compat_y_tst.o
execute
FAIL: tmpdir-gcc.dg-struct-layout-1/t021 c_compat_x_tst.o-c_compat_y_tst.o
execute
FAIL: tmpdir-gcc.dg-struct-layout-1/t022 c_compat_x_tst.o-c_compat_y_tst.o
execute
FAIL: tmpdir-gcc.dg-struct-layout-1/t023 c_compat_x_tst.o-c_compat_y_tst.o
execute
FAIL: tmpdir-gcc.dg-struct-layout-1/t024 c_compat_x_tst.o compile, (internal
compiler error)
FAIL: tmpdir-gcc.dg-struct-layout-1/t024 c_compat_y_tst.o compile, (internal
compiler error)
FAIL: tmpdir-gcc.dg-struct-layout-1/t025 c_compat_x_tst.o-c_compat_y_tst.o
execute
FAIL: tmpdir-gcc.dg-struct-layout-1/t026 c_compat_x_tst.o-c_compat_y_tst.o
execute
FAIL: tmpdir-gcc.dg-struct-layout-1/t027 c_compat_x_tst.o compile, (internal
compiler error)
FAIL: tmpdir-gcc.dg-struct-layout-1/t027 c_compat_y_tst.o compile, (internal
compiler error)
FAIL: tmpdir-gcc.dg-struct-layout-1/t028 c_compat_x_tst.o-c_compat_y_tst.o
execute
... (non-regressions elided)
Running
/tmp/hpautotest-gcc1/gcc/gcc/testsuite/gcc.dg/torture/stackalign/stackalign.exp
...
FAIL: gcc.dg/torture/stackalign/nested-1.c -O0 execution test
FAIL: gcc.dg/torture/stackalign/nested-2.c -O0 execution test
FAIL: gcc.dg/torture/stackalign/nested-2.c -O1 execution test
FAIL: gcc.dg/torture/stackalign/nested-2.c -O2 execution test
FAIL: gcc.dg/torture/stackalign/nested-2.c -Os execution test
FAIL: gcc.dg/torture/stackalign/nested-2.c -O2 -flto execution test
FAIL: gcc.dg/torture/stackalign/nested-2.c -O2 -fwhopr execution test
FAIL: gcc.dg/torture/stackalign/nested-3.c -O0 execution test
FAIL: gcc.dg/torture/stackalign/nested-3.c -O1 execution test
FAIL: gcc.dg/torture/stackalign/nested-3.c -O2 execution test
FAIL: gcc.dg/torture/stackalign/nested-3.c -Os execution test
FAIL: gcc.dg/torture/stackalign/nested-3.c -O2 -flto execution test
FAIL: gcc.dg/torture/stackalign/nested-3.c -O2 -fwhopr execution test
With the messages in the logfile being:
PASS: gcc.c-torture/execute/20060420-1.c compilation, -O1
program stopped with signal 6.^M
FAIL: gcc.c-torture/execute/20060420-1.c execution, -O1
...
PASS: gcc.c-torture/execute/simd-5.c compilation, -O0
program stopped with signal 6.^M
FAIL: gcc.c-torture/execute/simd-5.c execution, -O0
...
PASS: gcc.dg/compat/vector-1 c_compat_x_tst.o-c_compat_y_tst.o link
core: 4 byte misaligned write to address 0x68676665 at 0xeb0^M
program stopped with signal 10.^M
...
Executing on host: /tmp/hpautotest-gcc1/cris-elf/gccobj/gcc/xgcc
-B/tmp/hpautotest-gcc1/cris-elf/gccobj/gcc/ -w -I/tmp\
/hpautotest-gcc1/gcc/gcc/testsuite/gcc.dg/compat -Wno-abi -DSKIP_DECIMAL_FLOAT
-DSKIP_DECIMAL_FLOAT -c -isystem /tmp/\
hpautotest-gcc1/cris-elf/gccobj/cris-elf/./newlib/targ-include -isystem
/tmp/hpautotest-gcc1/gcc/newlib/libc/include -\
o c_compat_x_tst.o
/tmp/hpautotest-gcc1/cris-elf/gccobj/gcc/testsuite/gcc/gcc.dg-struct-layout-1//t001_x.c
(timeout \
= 300)
In file included from
/tmp/hpautotest-gcc1/cris-elf/gccobj/gcc/testsuite/gcc/gcc.dg-struct-layout-1//t001_x.c:9:0:^M
/tmp/hpautotest-gcc1/cris-elf/gccobj/gcc/testsuite/gcc/gcc.dg-struct-layout-1//t001_test.h:
In function 'test85':^M
/tmp/hpautotest-gcc1/cris-elf/gccobj/gcc/testsuite/gcc/gcc.dg-struct-layout-1//t001_test.h:86:1:
internal compiler erro\
r: Segmentation fault^M
...
PASS: tmpdir-gcc.dg-struct-layout-1/t002 c_compat_x_tst.o-c_compat_y_tst.o link
core: 4 byte misaligned read to address 0x871fd41f at 0x5500^M
program stopped with signal 10.^M
FAIL: tmpdir-gcc.dg-struct-layout-1/t002 c_compat_x_tst.o-c_compat_y_tst.o
execute
other messages similar.
Author of patches in suspect revision range CC:ed.
(I'll provide basic analysis for the execution failures if fixing the
compilation SEGV's don't fix them too.)
next reply other threads:[~2010-10-11 3:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 3:26 hp at gcc dot gnu.org [this message]
2010-10-11 17:27 ` [Bug rtl-optimization/45962] " rth at gcc dot gnu.org
2010-10-11 17:38 ` hp at gcc dot gnu.org
2010-10-11 17:38 ` hp at gcc dot gnu.org
2010-10-11 18:12 ` rth at gcc dot gnu.org
2010-10-11 22:46 ` [Bug middle-end/45962] " rth at gcc dot gnu.org
2010-10-12 2:31 ` hp at gcc dot gnu.org
2010-10-12 15:53 ` rth at gcc dot gnu.org
2010-10-12 15:55 ` rth at gcc dot gnu.org
2010-10-12 19:30 ` hp at gcc dot gnu.org
2010-10-12 20:23 ` hp at gcc dot gnu.org
2010-10-12 21:31 ` rth at gcc dot gnu.org
2010-10-12 21:55 ` hp at gcc dot gnu.org
2010-10-12 22:06 ` rth at gcc dot gnu.org
2010-10-12 22:16 ` hp at gcc dot gnu.org
2010-10-12 22:49 ` hp at gcc dot gnu.org
2010-10-19 2:38 ` hp at gcc dot gnu.org
2010-10-19 15:49 ` rth at gcc dot gnu.org
2010-10-19 22:22 ` hp at gcc dot gnu.org
2010-10-19 23:21 ` rth at gcc dot gnu.org
2010-11-03 15:39 ` rguenth at gcc dot gnu.org
2010-11-15 11:34 ` rguenth at gcc dot gnu.org
2011-03-11 4:42 ` hp at gcc dot gnu.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=bug-45962-4@http.gcc.gnu.org/bugzilla/ \
--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).