public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63594] [5 Regression] ICE: in ix86_vector_duplicate_value, at config/i386/i386.c:39831 with -mavx512f
Date: Tue, 21 Oct 2014 09:31:00 -0000 [thread overview]
Message-ID: <bug-63594-4-bc9lhUcyHq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63594-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63594
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Note that this bug shows up in quite a lot of regressions on the trunk, both
x86_64 and i686:
+FAIL: gcc.target/i386/avx-1.c (internal compiler error)
+FAIL: gcc.target/i386/avx-1.c (test for excess errors)
+FAIL: gcc.target/i386/avx-2.c (internal compiler error)
+FAIL: gcc.target/i386/avx-2.c (test for excess errors)
+FAIL: gcc.target/i386/avx512f-vec-init.c (internal compiler error)
+FAIL: gcc.target/i386/avx512f-vec-init.c (test for excess errors)
+UNRESOLVED: gcc.target/i386/avx512f-vec-init.c scan-assembler-times
vbroadcastsd 1
+UNRESOLVED: gcc.target/i386/avx512f-vec-init.c scan-assembler-times
vbroadcastss 1
+UNRESOLVED: gcc.target/i386/avx512f-vec-init.c scan-assembler-times vmovdqa64[
\\\\t]+%zmm 2
+UNRESOLVED: gcc.target/i386/avx512f-vec-init.c scan-assembler-times
vpbroadcastb 2
+UNRESOLVED: gcc.target/i386/avx512f-vec-init.c scan-assembler-times
vpbroadcastd 1
+UNRESOLVED: gcc.target/i386/avx512f-vec-init.c scan-assembler-times
vpbroadcastq 1
+UNRESOLVED: gcc.target/i386/avx512f-vec-init.c scan-assembler-times
vpbroadcastw 2
+FAIL: gcc.target/i386/sse-14.c (internal compiler error)
+FAIL: gcc.target/i386/sse-14.c (test for excess errors)
+FAIL: gcc.target/i386/sse-22.c (internal compiler error)
+FAIL: gcc.target/i386/sse-22.c (test for excess errors)
+FAIL: gcc.target/i386/sse-22a.c (internal compiler error)
+FAIL: gcc.target/i386/sse-22a.c (test for excess errors)
+FAIL: gcc.target/i386/sse-23.c (internal compiler error)
+FAIL: gcc.target/i386/sse-23.c (test for excess errors)
+FAIL: gcc.target/i386/sse-24.c (internal compiler error)
+FAIL: gcc.target/i386/sse-24.c (test for excess errors)
are all because of this, so IMHO this is quite urgent thing to solve.
Note, supposedly in the WIP2 patch supposedly the vec_dup<mode> and the new
define_insns should be moved after the avx512 patterns, so that those trigger
earlier, and as I said, IMHO they really need to be merged so that broadcasts
from gprs are in the same patterns as broadcasts from memory or vector regs,
just different alternatives, but supposedly that can be done incrementally.
I'm also not sure about the v vs. x constraints on the AVX2 insn, supposedly
v is not an option if the mode iterator includes V*QI and V*HI modes, because
then AVX512F doesn't have instructions for that, right?
next prev parent reply other threads:[~2014-10-21 9:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-63594-4@http.gcc.gnu.org/bugzilla/>
2014-10-19 19:04 ` ubizjak at gmail dot com
2014-10-20 9:15 ` jakub at gcc dot gnu.org
2014-10-20 10:39 ` jakub at gcc dot gnu.org
2014-10-20 12:50 ` kyukhin at gcc dot gnu.org
2014-10-20 17:05 ` jakub at gcc dot gnu.org
2014-10-20 17:16 ` jakub at gcc dot gnu.org
2014-10-21 9:31 ` jakub at gcc dot gnu.org [this message]
2014-10-22 7:00 ` jakub at gcc dot gnu.org
2014-10-22 7:24 ` jakub at gcc dot gnu.org
2014-10-24 7:04 ` trippels at gcc dot gnu.org
2014-11-18 14:54 ` jakub at gcc dot gnu.org
2014-11-20 12:38 ` rguenth at gcc dot gnu.org
2014-12-10 9:01 ` jakub 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-63594-4-bc9lhUcyHq@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).