public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/14981] [3.4/4.0 Regression] ICE in _mm_xor_pd for SSE2 with -O1
Date: Wed, 15 Dec 2004 04:23:00 -0000 [thread overview]
Message-ID: <20041215040913.19343.qmail@sourceware.org> (raw)
In-Reply-To: <20040416183851.14981.davide.rossetti@roma1.infn.it>
------- Additional Comments From rth at gcc dot gnu dot org 2004-12-15 04:09 -------
We should not ice, indeed, but the comment #18 test case -- with -msse
but not -msse2 -- is invalid. We should have stopped earlier, saying
that v2df is not available with sse1 only.
--
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at gcc dot gnu |rth at gcc dot gnu dot org
|dot org |
Status|NEW |ASSIGNED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14981
next prev parent reply other threads:[~2004-12-15 4:23 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 18:54 [Bug target/14981] New: " davide dot rossetti at roma1 dot infn dot it
2004-04-16 19:10 ` [Bug target/14981] " bangerth at dealii dot org
2004-04-16 19:15 ` bangerth at dealii dot org
2004-04-16 19:58 ` [Bug target/14981] [3.4 only] " pinskia at gcc dot gnu dot org
2004-04-19 14:56 ` pinskia at gcc dot gnu dot org
2004-04-20 2:34 ` [Bug target/14981] [3.3/3.4 Regression] " giovannibajo at libero dot it
2004-04-20 2:40 ` pinskia at gcc dot gnu dot org
2004-04-20 6:48 ` bangerth at dealii dot org
2004-04-20 7:18 ` pinskia at gcc dot gnu dot org
2004-06-06 3:53 ` giovannibajo at libero dot it
2004-06-21 21:16 ` mmitchel at gcc dot gnu dot org
2004-08-17 2:51 ` [Bug target/14981] [3.4/3.5 " reichelt at gcc dot gnu dot org
2004-08-29 18:12 ` mmitchel at gcc dot gnu dot org
2004-08-29 18:16 ` mmitchel at gcc dot gnu dot org
2004-10-21 3:17 ` [Bug target/14981] [3.4/4.0 " pinskia at gcc dot gnu dot org
2004-11-01 0:45 ` mmitchel at gcc dot gnu dot org
2004-11-30 15:59 ` [Bug target/14981] [3.4 " uros at gcc dot gnu dot org
2004-12-01 0:43 ` [Bug target/14981] [3.4/4.0 " reichelt at gcc dot gnu dot org
2004-12-01 6:50 ` uros at gcc dot gnu dot org
2004-12-02 9:49 ` [Bug target/14981] [3.4 " reichelt at gcc dot gnu dot org
2004-12-02 10:30 ` belyshev at lubercy dot com
2004-12-03 10:18 ` reichelt at gcc dot gnu dot org
2004-12-03 11:51 ` reichelt at gcc dot gnu dot org
2004-12-05 9:31 ` ebotcazou at gcc dot gnu dot org
2004-12-13 12:01 ` [Bug target/14981] [3.4/4.0 " reichelt at gcc dot gnu dot org
2004-12-14 8:53 ` ebotcazou at gcc dot gnu dot org
2004-12-15 4:23 ` rth at gcc dot gnu dot org [this message]
2004-12-15 12:18 ` rth at gcc dot gnu dot org
2004-12-15 12:24 ` rth at gcc dot gnu dot org
2005-03-21 6:22 ` uros at kss-loka dot si
2005-03-21 13:41 ` [Bug target/14981] [3.4 " uros at kss-loka dot si
2005-03-22 8:43 ` uros at kss-loka dot si
2005-03-22 15:54 ` cvs-commit at gcc dot gnu dot org
2005-03-22 16:02 ` uros at kss-loka dot si
2005-05-09 16:52 ` jakub at gcc dot gnu dot org
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=20041215040913.19343.qmail@sourceware.org \
--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).