From: Uros Bizjak <ubizjak@gmail.com>
To: Kirill Yukhin <kirill.yukhin@gmail.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
Richard Henderson <rth@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH i386 AVX512] [85/n] Add intrinsics headers.
Date: Thu, 23 Oct 2014 18:15:00 -0000 [thread overview]
Message-ID: <CAFULd4b8wCdxCzN03sM355fC0aDHcRQJPcaYnFkxV4yBKux2sA@mail.gmail.com> (raw)
In-Reply-To: <20141022124319.GH11644@msticlxl57.ims.intel.com>
On Wed, Oct 22, 2014 at 2:43 PM, Kirill Yukhin <kirill.yukhin@gmail.com> wrote:
> Hello,
> This patch introduces necessary AVX-512* intrinsics headers.
>
> Bootstrapped.
> AVX-512* tests on top of patch-set all pass
> under simulator.
>
> Is it ok for trunk?
>
> gcc/
> * config/i386/avx512bwintrin.h: New.
> * config/i386/avx512dqintrin.h: Ditto.
> * config/i386/avx512vlbwintrin.h: Ditto.
> * config/i386/avx512vldqintrin.h: Ditto.
> * config/i386/avx512vlintrin.h: Ditto.
> * config/i386/immintrin.h: Include avx512vlintrin.h, avx512bwintrin.h,
> avx512dqintrin.h, avx512vlbwintrin.h, avx512vldqintrin.h.
Well, I have checked that patch follows the established coding style,
that it has #defines that cover constant propagation for -O0 and has
(hopefully) correct target flags, and that is the maximum a human can
do. Testsuite (mostly gcc.target/i386/sse-{12,13, 14}.c and
g++.dg/other/i386-{2,3}.C will cover the rest.
Oh, a couple of headers still have 2013 for their copyright data.
Please change these to 2014.
Rubber stamped as OK.
Thanks,
Uros.
prev parent reply other threads:[~2014-10-23 18:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 12:48 Kirill Yukhin
2014-10-23 18:15 ` Uros Bizjak [this message]
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=CAFULd4b8wCdxCzN03sM355fC0aDHcRQJPcaYnFkxV4yBKux2sA@mail.gmail.com \
--to=ubizjak@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=kirill.yukhin@gmail.com \
--cc=rth@redhat.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).