public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sje at cup dot hp dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/23240] gcc.c-torture/execute/pr23135.c execution fails
Date: Thu, 08 Sep 2005 16:34:00 -0000	[thread overview]
Message-ID: <20050908163428.8524.qmail@sourceware.org> (raw)
In-Reply-To: <20050804212849.23240.jsm28@gcc.gnu.org>


------- Additional Comments From sje at cup dot hp dot com  2005-09-08 16:34 -------
This test uses vectors.  It looks like the vector code for IA64 was written and
tested on Linux (which is little-endian) and this test fails on HP-UX which is
big-endian.  The program below prints '1500 1300' on Linux but prints '1300
1500' on HP-UX.  I think endianness was not considered somewhere in the vector
code but I am not sure where.



typedef int __attribute__((vector_size (8))) vecint;
typedef int __attribute__((mode(SI))) siint;

vecint i = { 150, 100 };
vecint j = { 10, 13 };
vecint k;

union {
  vecint v;
  siint i[2];
} res;

int
main ()
{
  vecint k0, k1, k2, k3, k4, k5, k6, k7;

  k1 = i * j;
  res.v = k1;

  printf("%d %d\n", res.i[0], res.i[1]);

  exit (0);
}

-- 


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


  parent reply	other threads:[~2005-09-08 16:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-04 21:30 [Bug tree-optimization/23240] New: " jsm28 at gcc dot gnu dot org
2005-08-04 21:56 ` [Bug target/23240] " pinskia at gcc dot gnu dot org
2005-08-05 16:51 ` pinskia at gcc dot gnu dot org
2005-08-10 12:12 ` pinskia at gcc dot gnu dot org
2005-09-08 16:34 ` sje at cup dot hp dot com [this message]
     [not found] <bug-23240-230@http.gcc.gnu.org/bugzilla/>
2005-10-12 23:49 ` wilson at gcc dot gnu dot org
2005-10-23 22:57 ` pinskia 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=20050908163428.8524.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).