From: Uros Bizjak <ubizjak@gmail.com>
To: Ilya Tocar <tocarip.intel@gmail.com>
Cc: Jakub Jelinek <jakub@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH, i386, testsuite] FMA intrinsics
Date: Thu, 25 Aug 2011 10:46:00 -0000 [thread overview]
Message-ID: <CAFULd4YymZ+1o2fpOVBCbqWE5vGXxafb38Ki9YtcrwJphVSUSA@mail.gmail.com> (raw)
In-Reply-To: <CAFFGCRA7_oo810HjEtpdtirE4waw=DfXmiHx7ijMr0=xOQm1EQ@mail.gmail.com>
On Thu, Aug 25, 2011 at 10:18 AM, Ilya Tocar <tocarip.intel@gmail.com> wrote:
> Changelog:
>
> 2011-08-25 Ilya Tocar <ilya.tocar@intel.com>
>
> * config/i386/fmaintrin.h: New.
> * config.gcc: Add fmaintrin.h.
> * config/i386/i386.c
> * <ix86_builtins> (IX86_BUILTIN_VFMADDSS3): New.
> (IX86_BUILTIN_VFMADDSD3): Likewise.
(enum ix86_builtins) <IX86_...>: New.
<IX86_...>: Likewise.
> * config/i386/sse.md (fmai_vmfmadd_<mode>): New.
> (*fmai_fmadd_<mode>): Likewise.
> (*fmai_fmsub_<mode>): Likewise.
> (*fmai_fnmadd_<mode>): Likewise.
> (*fmai_fnmsub_<mode>): Likewise.
> * config/i386/x86intrin.h: Add fmaintrin.h.
>
> And Changelog for testsuite:
>
> 2011-08-25 Ilya Tocar <ilya.tocar@intel.com>
>
> * gcc.target/i386/fma-check.h: New.
> * gcc.target/i386/fma-256-fmaddXX.c: New testcase.
> * gcc.target/i386/fma-256-fmaddsubXX.c: Likewise.
> * gcc.target/i386/fma-256-fmsubXX.c: Likewise.
> * gcc.target/i386/fma-256-fmsubaddXX.c: Likewise.
> * gcc.target/i386/fma-256-fnmaddXX.c: Likewise.
> * gcc.target/i386/fma-256-fnmsubXX.c: Likewise.
> * gcc.target/i386/fma-fmaddXX.c: Likewise.
> * gcc.target/i386/fma-fmaddsubXX.c: Likewise.
> * gcc.target/i386/fma-fmsubXX.c: Likewise.
> * gcc.target/i386/fma-fmsubaddXX.c: Likewise.
> * gcc.target/i386/fma-fnmaddXX.c: Likewise.
> * gcc.target/i386/fma-fnmsubXX.c: Likewise.
> * gcc.target/i386/fma-compile.c: Likewise.
> * gcc.target/i386/i386.exp (check_effective_target_fma): New.
> * gcc.target/i386/sse-12.c: Add -mfma.
> * gcc.target/i386/sse-13.c: Likewise.
> * gcc.target/i386/sse-14.c: Likewise.
> * gcc.target/i386/sse-22.c: Likewise.
> * gcc.target/i386/sse-23.c: Likewise.
> * gcc.target/i386/sse-13.c: Likewise.
Duplicate.
> * g++.dg/other/i386-2.c: Likewise.
*g++.dg/other/i386-2.C
> * g++.dg/other/i386-2.c: Likewise.
* g++.dg/other/i386-3.C
Uros.
next prev parent reply other threads:[~2011-08-25 9:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-20 11:23 Uros Bizjak
2011-08-22 17:32 ` Ilya Tocar
2011-08-22 20:41 ` Uros Bizjak
2011-08-23 14:55 ` Ilya Tocar
2011-08-23 15:33 ` Uros Bizjak
2011-08-24 10:06 ` Ilya Tocar
2011-08-24 10:12 ` Jakub Jelinek
2011-08-24 11:12 ` Ilya Tocar
2011-08-24 13:31 ` Uros Bizjak
2011-08-24 13:52 ` Ilya Tocar
2011-08-24 22:00 ` Uros Bizjak
2011-08-25 10:15 ` Ilya Tocar
2011-08-25 10:46 ` Uros Bizjak [this message]
2011-08-25 11:46 ` Ilya Tocar
2011-08-25 11:46 ` Jakub Jelinek
2011-08-25 11:49 ` Ilya Tocar
2011-08-26 11:03 ` Ilya Tocar
2011-08-26 14:07 ` H.J. Lu
2011-08-26 15:47 ` Ilya Tocar
2011-08-26 17:02 ` H.J. Lu
2011-08-26 17:06 ` H.J. Lu
2011-08-30 12:05 ` Ilya Tocar
2011-08-30 14:02 ` H.J. Lu
2011-08-30 14:10 ` Ilya Tocar
2011-08-30 14:32 ` Ilya Tocar
2011-08-30 15:25 ` H.J. Lu
-- strict thread matches above, loose matches on Subject: below --
2011-08-17 14:08 [PATCH, i386, testsuite]FMA intrinsics Ilya Tocar
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=CAFULd4YymZ+1o2fpOVBCbqWE5vGXxafb38Ki9YtcrwJphVSUSA@mail.gmail.com \
--to=ubizjak@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=tocarip.intel@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).