public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sa Liu <SALIU@de.ibm.com>
To: "Andrew Pinski" <pinskia@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH, spu] fix wrong parameter type in spu intrinsics
Date: Fri, 08 Feb 2008 14:58:00 -0000	[thread overview]
Message-ID: <OF207CDC92.D3A0AB98-ONC12573E9.004699DF-C12573E9.0046FA12@de.ibm.com> (raw)
In-Reply-To: <de8d50360802071853u79a952e1p33e20bc0408a05c1@mail.gmail.com>

"Andrew Pinski" <pinskia@gmail.com> wrote on 08.02.2008 03:53:18:

> This is ok with testcases and a changelog entry.

Ok, patch committed and added test case intrinsics-3.c to 
testsuite/gcc.target/spu/.

Index: gcc/gcc/testsuite/gcc.target/spu/intrinsics-3.c
===================================================================
--- /dev/null
+++ gcc/gcc/testsuite/gcc.target/spu/intrinsics-3.c
@@ -0,0 +1,21 @@
+/* { dg-do compile } */
+#include <spu_intrinsics.h>
+void f0 (vec_uint4 *in)
+{
+  vec_float4 out = spu_convtf (in[0], 128); /* { dg-error "expects an 
integer literal in the range" "0, 127"  }*/
+}
+
+void f1 (vec_int4 *in)
+{
+  vec_float4 out = spu_convtf (in[0], 128); /* { dg-error "expects an 
integer literal in the range" "0, 127"  }*/
+}
+
+void f2 (vec_float4 *in)
+{
+  vec_int4 out = spu_convts (in[0], 128); /* { dg-error "expects an 
integer literal in the range" "0, 127"  }*/
+}
+
+void f3 (vec_float4 *in)
+{
+  vec_uint4 out = spu_convtu (in[0], 128); /* { dg-error "expects an 
integer literal in the range" "0, 127"  }*/
+}


Thanks!
Sa

      reply	other threads:[~2008-02-08 12:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05 14:07 Sa Liu
2008-02-08  3:04 ` Andrew Pinski
2008-02-08 14:58   ` Sa Liu [this message]

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=OF207CDC92.D3A0AB98-ONC12573E9.004699DF-C12573E9.0046FA12@de.ibm.com \
    --to=saliu@de.ibm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=pinskia@gmail.com \
    /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).