public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tmsriram at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/58115] testcase gcc.target/i386/intrinsics_4.c failure
Date: Mon, 14 Oct 2013 16:55:00 -0000	[thread overview]
Message-ID: <bug-58115-4-Hn18W3jQhE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58115-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Sriraman Tallam <tmsriram at google dot com> ---
(In reply to Bernd Edlinger from comment #1)
> Hi Sriraman,
> 
> I'm putting you on CC since you are the author of that test case:
> I am not sure if the test case should use -msse2 instead of -msse,
> but running on an assertion is certainly to be avoided in any case.

I do not see why it *should* use msse2. Using msse2 however is perfectly fine
as it preserves the test case's intent.

Thanks
Sri

> 
> Regards
> Bernd.


  parent reply	other threads:[~2013-10-14 16:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09 22:23 [Bug target/58115] New: " bernd.edlinger at hotmail dot de
2013-08-09 22:31 ` [Bug target/58115] " bernd.edlinger at hotmail dot de
2013-10-14 13:10 ` ro at gcc dot gnu.org
2013-10-14 16:55 ` tmsriram at google dot com [this message]
2013-10-14 17:52 ` bernd.edlinger at hotmail dot de
2013-10-14 19:25 ` ubizjak at gmail dot com
2013-10-15  6:57 ` bernd.edlinger at hotmail dot de
2013-11-01 16:41 ` bernd.edlinger at hotmail dot de
2013-11-01 19:00 ` bernd.edlinger at hotmail dot de
2013-12-02 18:00 ` edlinger at gcc dot gnu.org
2013-12-17 18:26 ` bernd.edlinger at hotmail dot de
2014-01-06 16:34 ` edlinger at gcc dot gnu.org
2014-01-06 17:03 ` bernd.edlinger at hotmail dot de
2014-01-07 15:26 ` rsandifo at gcc dot gnu.org
2014-01-09 18:25 ` jakub at gcc dot gnu.org
2014-01-11 18:58 ` dje at gcc dot gnu.org
2014-02-12 17:51 ` bernd.edlinger at hotmail dot de

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-58115-4-Hn18W3jQhE@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).