public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "uros at kss-loka dot si" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/17767] [4.0 Regression] MMX intrinsics cause internal compiler error
Date: Tue, 21 Dec 2004 13:49:00 -0000 [thread overview]
Message-ID: <20041221134715.8181.qmail@sourceware.org> (raw)
In-Reply-To: <20041001072853.17767.jochang@gmail.com>
------- Additional Comments From uros at kss-loka dot si 2004-12-21 13:47 -------
The problem here is that case RTX_COMPARE:/case RTX_COMM_COMPARE: in fold_rtx()
in cse.c is not 'vector safe'. The testcase from comment #3 will trigger these
parts of RTX_COMPARE case:
/* See if the two operands are the same. */
if (folded_arg0 == folded_arg1 ...
Operands are the same, (reg:V4HI 62 [ D.1293 ]) and (reg:V4HI 62 [ D.1293 ]).
/* Sadly two equal NaNs are not equivalent. */
if (!HONOR_NANS (mode_arg0))
return ((code == EQ || code == LE || code == GE
|| code == LEU || code == GEU || code == UNEQ
|| code == UNLE || code == UNGE
|| code == ORDERED)
? true_rtx : false_rtx);
V4HI mode obviously does not HONOR_NANS and (code == EQ). A 'true_rtx' is
returned, but a _vector_ of trues would be more appropriate in this case.
I guess the RTX_COMPARE case should be recoded for vector support, or patch from
comment #7 should be used to prevent VECTOR_MODES from entering this code.
Uros.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17767
next prev parent reply other threads:[~2004-12-21 13:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 7:28 [Bug inline-asm/17767] New: " jochang at gmail dot com
2004-10-01 7:32 ` [Bug inline-asm/17767] " jochang at gmail dot com
2004-10-01 12:36 ` [Bug target/17767] " pinskia at gcc dot gnu dot org
2004-10-01 13:32 ` [Bug target/17767] [3.4/4.0 Regression] " pinskia at gcc dot gnu dot org
2004-10-01 14:18 ` reichelt at gcc dot gnu dot org
2004-10-01 14:34 ` pinskia at gcc dot gnu dot org
2004-10-01 17:49 ` pinskia at gcc dot gnu dot org
2004-10-11 9:42 ` [Bug target/17767] [4.0 " reichelt at gcc dot gnu dot org
2004-11-28 21:43 ` pinskia at gcc dot gnu dot org
2004-12-10 15:34 ` uros at kss-loka dot si
2004-12-12 17:59 ` pinskia at gcc dot gnu dot org
2004-12-16 18:19 ` pinskia at gcc dot gnu dot org
2004-12-21 13:49 ` uros at kss-loka dot si [this message]
2005-01-04 9:22 ` [Bug middle-end/17767] " uros at kss-loka dot si
2005-01-04 15:44 ` cvs-commit at gcc dot gnu dot org
2005-01-04 15:46 ` pinskia at gcc dot gnu dot org
2005-02-17 13:20 ` cvs-commit 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=20041221134715.8181.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).