public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "uros at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/56788] _mm_frcz_sd and _mm_frcz_ss ignore their second argument
Date: Thu, 28 Nov 2013 16:48:00 -0000	[thread overview]
Message-ID: <bug-56788-4-D9hofNGa8j@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56788-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56788

--- Comment #16 from uros at gcc dot gnu.org ---
Author: uros
Date: Thu Nov 28 16:48:44 2013
New Revision: 205495

URL: http://gcc.gnu.org/viewcvs?rev=205495&root=gcc&view=rev
Log:
    Backport from mainline
    2013-11-23  Uros Bizjak  <ubizjak@gmail.com>

    PR target/56788
    * config/i386/i386.c (bdesc_multi_arg) <IX86_BUILTIN_VFRCZSS>:
    Declare as MULTI_ARG_1_SF instruction.
    <IX86_BUILTIN_VFRCZSD>: Decleare as MULTI_ARG_1_DF instruction.
    * config/i386/sse.md (*xop_vmfrcz<mode>2): Rename
    from *xop_vmfrcz_<mode>.
    * config/i386/xopintrin.h (_mm_frcz_ss): Use __builtin_ia32_movss
    to merge scalar result with __A.
    (_mm_frcz_sd): Use __builtin_ia32_movsd to merge scalar
    result with __A.

testsuite/ChangeLog:

    Backport from mainline
    2013-11-27  Uros Bizjak  <ubizjak@gmail.com>
            Ganesh Gopalasubramanian  <Ganesh.Gopalasubramanian@amd.com>

    PR target/56788
    * gcc.target/i386/xop-frczX.c: New test.


Added:
    branches/gcc-4_8-branch/gcc/testsuite/gcc.target/i386/xop-frczX.c
Modified:
    branches/gcc-4_8-branch/gcc/ChangeLog
    branches/gcc-4_8-branch/gcc/config/i386/i386.c
    branches/gcc-4_8-branch/gcc/config/i386/sse.md
    branches/gcc-4_8-branch/gcc/config/i386/xopintrin.h
    branches/gcc-4_8-branch/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2013-11-28 16:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-30 20:20 [Bug target/56788] New: " glisse at gcc dot gnu.org
2013-03-30 20:42 ` [Bug target/56788] " glisse at gcc dot gnu.org
2013-06-27 13:05 ` glisse at gcc dot gnu.org
2013-11-23  9:09 ` ubizjak at gmail dot com
2013-11-23  9:19 ` ubizjak at gmail dot com
2013-11-23  9:22 ` ubizjak at gmail dot com
2013-11-23  9:34 ` glisse at gcc dot gnu.org
2013-11-23  9:45 ` ubizjak at gmail dot com
2013-11-23 11:39 ` ubizjak at gmail dot com
2013-11-23 12:10 ` glisse at gcc dot gnu.org
2013-11-23 13:00 ` glisse at gcc dot gnu.org
2013-11-27 18:07 ` uros at gcc dot gnu.org
2013-11-28 16:48 ` uros at gcc dot gnu.org [this message]
2013-11-28 18:14 ` uros at gcc dot gnu.org
2013-11-28 18:15 ` ubizjak at gmail dot com

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-56788-4-D9hofNGa8j@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).