public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: opaque vector types?
Date: Wed, 06 May 2009 06:29:00 -0000	[thread overview]
Message-ID: <xnmy9qvj51.fsf@greed.delorie.com> (raw)
In-Reply-To: <de8d50360905052311g670513b3l6d51c8ed4c6b03f9@mail.gmail.com> (Andrew Pinski's message of "Tue\, 5 May 2009 23\:11\:02 -0700")


Andrew Pinski <pinskia@gmail.com> writes:
> 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.

Thanks, I'll look at those.  Any way to prototype such functions in C ?

  reply	other threads:[~2009-05-06  6:29 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
2009-05-06  6:29   ` DJ Delorie [this message]
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=xnmy9qvj51.fsf@greed.delorie.com \
    --to=dj@redhat.com \
    --cc=gcc@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).