public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Uros Bizjak <ubizjak@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Kirill Yukhin <kirill.yukhin@gmail.com>,
		"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix and improve avx2 broadcasts (PR target/63594)
Date: Wed, 22 Oct 2014 06:17:00 -0000	[thread overview]
Message-ID: <CAFULd4bGoS7Kd4qzWOPskBiVLFgzT3GBTMiF5frpw2TF9UW_zw@mail.gmail.com> (raw)
In-Reply-To: <20141021161037.GA10376@tucnak.redhat.com>

On Tue, Oct 21, 2014 at 6:10 PM, Jakub Jelinek <jakub@redhat.com> wrote:
> Hi!
>
> This patch fixes a bunch of recent regressions:
> 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)
> and improves quality of code generated for AVX2 and AVX512F broadcasts;
> as AVX2 broadcast instructions can have source in memory or vector register
> (but only AVX512F can have it in GPRs), the patch adds splitter for the
> GPR case and adds ! for that, so that RA can choose what is best and if
> broadcast from GPR is desirable, it first performs vmovd from GPR into
> the dest register and then vpbroadcast{b,w,d} it.
>
> The AVX512* patterns should be IMHO merged, so that whether GPR or MEM is used
> are just alternatives of the same define_insn rather than different define_insns,
> but am not changing that right now, will leave that to Kirill as a follow-up.
>
> Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
>
> 2014-10-21  Jakub Jelinek  <jakub@redhat.com>
>
>         PR target/63594
>         * config/i386/i386.c (ix86_expand_vector_init_duplicate): For
>         V{8HI,16QI,16HI,32QI}mode call ix86_vector_duplicate_value
>         even for just TARGET_AVX2, not only for
>         TARGET_AVX512VL && TARGET_AVX512BW.  For V{32HI,64QI}mode,
>         call ix86_vector_duplicate_value only if TARGET_AVX512BW,
>         otherwise build it using concatenation of 256-bit
>         broadcast.
>         * config/i386/sse.md (AVX_VEC_DUP_MODE): Moved after
>         avx512 broadcast patterns.
>         (vec_dup<mode>): Likewise.  For avx2 use
>         v<sseintprefix>broadcast<bcstscalarsuff> instead of
>         vbroadcast<ssescalarmodesuffix>.
>         (AVX2_VEC_DUP_MODE): New mode iterator.
>         (*vec_dup<mode>): New TARGET_AVX2 define_insn with
>         AVX2_VEC_DUP_MODE iterator, add a splitter for that.
>
>         * gcc.dg/pr63594-1.c: New test.
>         * gcc.dg/pr63594-2.c: New test.
>         * gcc.target/i386/sse2-pr63594-1.c: New test.
>         * gcc.target/i386/sse2-pr63594-2.c: New test.
>         * gcc.target/i386/avx-pr63594-1.c: New test.
>         * gcc.target/i386/avx-pr63594-2.c: New test.
>         * gcc.target/i386/avx2-pr63594-1.c: New test.
>         * gcc.target/i386/avx2-pr63594-2.c: New test.
>         * gcc.target/i386/avx512f-pr63594-1.c: New test.
>         * gcc.target/i386/avx512f-pr63594-2.c: New test.
>         * gcc.target/i386/avx512f-vec-init.c: Adjust expected
>         insn counts.

OK.

Thanks,
Uros.

  reply	other threads:[~2014-10-22  5:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21 16:13 Jakub Jelinek
2014-10-22  6:17 ` Uros Bizjak [this message]
2014-10-23 13:00 ` Rainer Orth
2014-10-23 13:14   ` Jakub Jelinek
2014-10-23 13:24     ` Rainer Orth
2014-10-24  9:35       ` Rainer Orth
2014-11-29 22:21 ` H.J. Lu

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=CAFULd4bGoS7Kd4qzWOPskBiVLFgzT3GBTMiF5frpw2TF9UW_zw@mail.gmail.com \
    --to=ubizjak@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=kirill.yukhin@gmail.com \
    /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).