From: Steve Ellcey <sje@cup.hp.com>
To: gcc-patches@gcc.gnu.org
Subject: Patch to fix vector tests on IA64 HP-UX
Date: Fri, 01 Jun 2007 20:27:00 -0000 [thread overview]
Message-ID: <200706012027.NAA21688@hpsje.cup.hp.com> (raw)
A number of vect tests are failing on IA64 HP-UX because we are swapping
vector elements when we shouldn't be. This patch removes the BIG_ENDIAN
test and does the same thing for both big and little endian platforms.
Tested on IA64 HP-UX and Linux, it caused no regressions on Linux and
on HP-UX it fixes:
FAIL: gcc.dg/vect/no-tree-dom-vect-bug.c execution test
FAIL: gcc.dg/vect/pr30784.c execution test
FAIL: gcc.dg/vect/vect-14.c execution test
FAIL: gcc.dg/vect/vect-14.c execution test
FAIL: gcc.dg/vect/vect-iv-10.c execution test
FAIL: gcc.dg/vect/vect-iv-10.c execution test
FAIL: gcc.dg/vect/vect-iv-2.c execution test
FAIL: gcc.dg/vect/vect-iv-2.c execution test
FAIL: gcc.dg/vect/vect-iv-3.c execution test
FAIL: gcc.dg/vect/vect-iv-3.c execution test
OK to checkin? Maybe it is obvious.
Steve Ellcey
sje@cup.hp.com
2007-06-01 Steve Ellcey <sje@cup.hp.com>
* config/ia64/vect.md (vec_initv2si): Remove bad BIG_ENDIAN test.
Index: config/ia64/vect.md
===================================================================
--- config/ia64/vect.md (revision 125253)
+++ config/ia64/vect.md (working copy)
@@ -802,8 +802,8 @@ (define_expand "vec_initv2si"
if (GET_CODE (op1) == CONST_INT && GET_CODE (op2) == CONST_INT)
{
rtvec v = rtvec_alloc (2);
- RTVEC_ELT (v, 0) = TARGET_BIG_ENDIAN ? op2 : op1;
- RTVEC_ELT (v, 1) = TARGET_BIG_ENDIAN ? op1 : op2;;
+ RTVEC_ELT (v, 0) = op1;
+ RTVEC_ELT (v, 1) = op2;
x = gen_rtx_CONST_VECTOR (V2SImode, v);
emit_move_insn (operands[0], x);
DONE;
next reply other threads:[~2007-06-01 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 20:27 Steve Ellcey [this message]
2007-07-27 20:30 ` Steve Ellcey
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=200706012027.NAA21688@hpsje.cup.hp.com \
--to=sje@cup.hp.com \
--cc=gcc-patches@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).