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 regression/55167] New: [4.8 Regression]: g++.dg/other/vector-compare.C, ICE
Date: Thu, 01 Nov 2012 18:47:00 -0000 [thread overview]
Message-ID: <bug-55167-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55167
Bug #: 55167
Summary: [4.8 Regression]: g++.dg/other/vector-compare.C, ICE
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: regression
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: hp@gcc.gnu.org
CC: glisse@gcc.gnu.org
Host: x86_64-unknown-linux-gnu
Target: cris-axis-elf
This test previously passed, now it fails.
A patch in the revision range (last_known_working:first_known_failing)
192985:192991
exposed or caused this regression. Since then it fails as follows:
Running /tmp/hpautotest-gcc0/gcc/gcc/testsuite/g++.dg/dg.exp ...
FAIL: g++.dg/other/vector-compare.C (internal compiler error)
FAIL: g++.dg/other/vector-compare.C (test for excess errors)
In g++.log:
Executing on host:
/tmp/hpautotest-gcc0/cris-elf/gccobj/gcc/testsuite/g++/../../g++
-B/tmp/hpautotest-gcc0/cris-elf/gccobj/gcc/testsuite/g++/../../
/tmp/hpautotest-gcc0/gcc/gcc/testsuite/g++.dg/other/vector-compare.C
-fno-diagnostics-show-caret -nostdinc++
-I/tmp/hpautotest-gcc0/cris-elf/gccobj/cris-elf/libstdc++-v3/include/cris-elf
-I/tmp/hpautotest-gcc0/cris-elf/gccobj/cris-elf/libstdc++-v3/include
-I/tmp/hpautotest-gcc0/gcc/libstdc++-v3/libsupc++
-I/tmp/hpautotest-gcc0/gcc/libstdc++-v3/include/backward
-I/tmp/hpautotest-gcc0/gcc/libstdc++-v3/testsuite/util -fmessage-length=0
-std=gnu++11 -Wall -S -isystem
/tmp/hpautotest-gcc0/cris-elf/gccobj/cris-elf/./newlib/targ-include -isystem
/tmp/hpautotest-gcc0/gcc/newlib/libc/include -o vector-compare.s (timeout =
300)
/tmp/hpautotest-gcc0/gcc/gcc/testsuite/g++.dg/other/vector-compare.C: In
function 'int main()':
/tmp/hpautotest-gcc0/gcc/gcc/testsuite/g++.dg/other/vector-compare.C:30:21:
internal compiler error: Segmentation fault
0x9fc565 crash_signal
/tmp/hpautotest-gcc0/gcc/gcc/toplev.c:333
0x802f65 force_operand(rtx_def*, rtx_def*)
/tmp/hpautotest-gcc0/gcc/gcc/expr.c:6975
0x743ac0 expand_gimple_stmt_1
/tmp/hpautotest-gcc0/gcc/gcc/cfgexpand.c:2168
0x743ac0 expand_gimple_stmt
/tmp/hpautotest-gcc0/gcc/gcc/cfgexpand.c:2204
0x744b39 expand_gimple_basic_block
/tmp/hpautotest-gcc0/gcc/gcc/cfgexpand.c:3979
0x746276 gimple_expand_cfg
/tmp/hpautotest-gcc0/gcc/gcc/cfgexpand.c:4498
According to <http://gcc.gnu.org/ml/gcc-patches/2012-10/msg02858.html>, this
also happens for i686-linux and revision r192986 is to blame.
Author of suspect patch CC:ed.
next reply other threads:[~2012-11-01 18:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 18:47 hp at gcc dot gnu.org [this message]
2012-11-01 19:05 ` [Bug regression/55167] " glisse at gcc dot gnu.org
2012-11-01 19:52 ` hp at gcc dot gnu.org
2012-11-01 20:22 ` glisse at gcc dot gnu.org
2012-11-02 5:34 ` hp at gcc dot gnu.org
2012-11-02 8:31 ` glisse 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-55167-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).