public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/68124] [6 Regression] Many i386 test failures
Date: Tue, 27 Oct 2015 23:44:00 -0000 [thread overview]
Message-ID: <bug-68124-4-MK0ZZObedI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-68124-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68124
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rth at gcc dot gnu.org
--- Comment #1 from H.J. Lu <hjl.tools at gmail dot com> ---
It was cased by r229458:
[hjl@gnu-ivb-1 gcc]$ ./xgcc -B./ -march=corei7 -O3 -mavx2 -S
/export/gnu/import/git/gcc-regression/gcc/gcc/testsuite/gcc.target/i386/pr58137.c
-m32
/export/gnu/import/git/gcc-regression/gcc/gcc/testsuite/gcc.target/i386/pr58137.c:
In function \u2018more_xrv\u2019:
/export/gnu/import/git/gcc-regression/gcc/gcc/testsuite/gcc.target/i386/pr58137.c:33:1:
internal compiler error: in gen_reg_rtx, at emit-rtl.c:1031
}
^
0x99ad69 gen_reg_rtx(machine_mode)
../../../../gcc/gcc/emit-rtl.c:1031
0x9bae10 copy_to_reg(rtx_def*)
../../../../gcc/gcc/explow.c:570
0xd26e50 gen_lowpart_general(machine_mode, rtx_def*)
../../../../gcc/gcc/rtlhooks.c:62
0x13fddbb gen_split_392(rtx_insn*, rtx_def**)
../../../../gcc/gcc/config/i386/sse.md:17100
0x15ab55b split_23
../../../../gcc/gcc/config/i386/sse.md:17098
0x15ac314 split_24
../../../../gcc/gcc/config/i386/i386.md:4803
0x15afe7c split_insns(rtx_def*, rtx_insn*)
../../../../gcc/gcc/config/i386/i386.md:15867
0x9a1011 try_split(rtx_def*, rtx_insn*, int)
../../../../gcc/gcc/emit-rtl.c:3666
0xcbce89 split_insn
../../../../gcc/gcc/recog.c:2874
0xcbd161 split_all_insns()
../../../../gcc/gcc/recog.c:2964
0xcbef85 rest_of_handle_split_after_reload
../../../../gcc/gcc/recog.c:3902
0xcbefd6 execute
../../../../gcc/gcc/recog.c:3931
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
[hjl@gnu-ivb-1 gcc]$
next prev parent reply other threads:[~2015-10-27 23:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 22:34 [Bug target/68124] New: " hjl.tools at gmail dot com
2015-10-27 23:44 ` hjl.tools at gmail dot com [this message]
2015-10-27 23:46 ` [Bug target/68124] " hjl.tools at gmail dot com
2015-10-28 1:29 ` hjl.tools at gmail dot com
2015-10-28 19:40 ` rth at gcc dot gnu.org
2015-10-28 20:16 ` rth at gcc dot gnu.org
2015-10-28 20:27 ` hjl.tools at gmail dot com
2015-10-28 20:46 ` rth at gcc dot gnu.org
2015-10-29 7:46 ` rth at gcc dot gnu.org
2015-10-29 14:17 ` hjl.tools at gmail dot com
2015-10-29 18:37 ` rth at gcc dot gnu.org
2015-10-29 18:44 ` rth 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-68124-4-MK0ZZObedI@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).