From: Andrew Pinski <pinskia@gmail.com>
To: DJ Delorie <dj@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: opaque vector types?
Date: Wed, 06 May 2009 06:11:00 -0000 [thread overview]
Message-ID: <de8d50360905052311g670513b3l6d51c8ed4c6b03f9@mail.gmail.com> (raw)
In-Reply-To: <200905060604.n4664Skm024765@greed.delorie.com>
On Tue, May 5, 2009 at 11:04 PM, DJ Delorie <dj@redhat.com> wrote:
> I'm working on a coprocessor which has separate SIMD arithmetic
> operations for each data size, but only one SIMD logical operation for
> all sizes. I.e. there's four ADD insns (V8QI, V4HI, etc) , but only
> one AND insn. I'd like to use an opaque vector type for the AND
> builtin, to avoid warnings.
You could do what the rs6000 back-end does for the altivec builtins
and resolve them while the parser is run (the SPU back-end does the
same thing too). Yes there are opaque vector types, you just use
build_opaque_vector_type instead of build_vector_type.
-- Pinski
next prev parent reply other threads:[~2009-05-06 6:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 6:04 DJ Delorie
2009-05-06 6:11 ` Andrew Pinski [this message]
2009-05-06 6:29 ` DJ Delorie
2009-05-06 9:08 ` Paolo Bonzini
2009-05-08 21:05 ` Michael Meissner
2009-06-10 13:00 ` Paul Brook
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=de8d50360905052311g670513b3l6d51c8ed4c6b03f9@mail.gmail.com \
--to=pinskia@gmail.com \
--cc=dj@redhat.com \
--cc=gcc@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).