public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <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: Sat, 23 Nov 2013 09:19:00 -0000 [thread overview]
Message-ID: <bug-56788-4-K8GDukaXqP@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
Uroš Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |4.7.4
--- Comment #4 from Uroš Bizjak <ubizjak at gmail dot com> ---
gcc follows Microsoft definition [1]:
__m128d _mm_frcz_ss (
__m128 high,
__m128 src
);
This should be the same as other "vm" (vector merge) instructions, for example
_mm_add_ss [2], also commented in gcc's xmmintrin.h:
/* Perform the respective operation on the lower SPFP (single-precision
floating-point) values of A and B; the upper three SPFP values are
passed through from A. */
__m128 _mm_add_ss (__m128 __A, __m128 __B)
{
return (__m128) __builtin_ia32_addss ((__v4sf)__A, (__v4sf)__B);
}
[1] http://msdn.microsoft.com/en-us/library/vstudio/gg445126%28v=vs.100%29.aspx
[2] http://msdn.microsoft.com/en-us/library/be94x2y6%28v=vs.90%29.aspx
>From gcc-bugs-return-435604-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 23 09:20:58 2013
Return-Path: <gcc-bugs-return-435604-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31628 invoked by alias); 23 Nov 2013 09:20:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 31596 invoked by uid 48); 23 Nov 2013 09:20:55 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/59228] ICE-on-invalid with assumed type and ASYNCHRONOUS
Date: Sat, 23 Nov 2013 09:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: janus at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-59228-4-qApu5i9T7T@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59228-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59228-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2013-11/txt/msg02381.txt.bz2
Content-length: 627
http://gcc.gnu.org/bugzilla/show_bug.cgi?idY228
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from janus at gcc dot gnu.org ---
Fixed on trunk with r205304. Despite the fact that it might be viewed as a
regression, I don't think it's worth backporting to 4.8 (given that it's 'only'
ICE-on-invalid and was reported against trunk).
Closing as fixed. Thanks for the report!
next prev parent reply other threads:[~2013-11-23 9:19 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 [this message]
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
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-K8GDukaXqP@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).