public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/30210] Altivec builtins return wrong types
Date: Thu, 14 Dec 2006 17:30:00 -0000 [thread overview]
Message-ID: <20061214172955.20997.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30210-9531@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from pinskia at gcc dot gnu dot org 2006-12-14 17:29 -------
(In reply to comment #1)
> Builtin vmuloub has always returned "wrong" types, because it derives its types
> simply from the modes of the altivec_vmuloub pattern.
Except that is wrong. Look at the altivec PIM and you will see it returns
vector unsigned short.
Take the following testcase:
#include <altivec.h>
vector unsigned short f(vector unsigned char a, vector unsigned char b)
{
return vec_vmuloub(a, b);
}
This should work even if we cannot assign from vector signed short to vector
unsigend short.
I think this whole type issue is a mess and needs some improvement.
Maybe next week I can get to that.
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2006-12-14 17:29:55
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30210
next prev parent reply other threads:[~2006-12-14 17:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 11:51 [Bug target/30210] New: " irar at il dot ibm dot com
2006-12-14 17:23 ` [Bug target/30210] " bonzini at gnu dot org
2006-12-14 17:30 ` pinskia at gcc dot gnu dot org [this message]
2006-12-14 17:46 ` bonzini at gnu dot org
2006-12-15 12:05 ` bonzini at gnu dot org
2006-12-20 12:20 ` irar at il dot ibm dot com
2006-12-20 12:29 ` [Bug target/30210] Altivec builtins have inaccurate return types bonzini at gnu dot org
2006-12-20 15:25 ` bonzini at gnu dot org
2007-01-15 10:04 ` irar at il dot ibm dot com
2009-05-03 14:25 ` bonzini at gnu dot org
2009-05-03 14:26 ` bonzini at gnu dot org
2009-05-03 15:54 ` rguenth at gcc dot gnu dot org
2009-05-03 15:56 ` rguenth at gcc dot gnu dot org
2009-05-03 15:57 ` [Bug target/30210] [4.5 Regression] " rguenth at gcc dot gnu dot org
2009-05-05 16:14 ` mmitchel at gcc dot gnu dot org
2009-06-12 12:20 ` pinskia at gcc dot gnu dot org
2009-07-08 21:03 ` rguenth at gcc dot gnu dot org
2009-07-08 21:04 ` rguenth at gcc dot gnu dot org
2009-07-08 23:42 ` meissner at linux dot vnet dot ibm dot com
2009-10-22 21:34 ` 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=20061214172955.20997.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).