public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Marc Glisse <marc.glisse@inria.fr>
Cc: Jason Merrill <jason@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [C++] Fix __builtin_shuffle
Date: Thu, 27 Jun 2013 16:09:00 -0000	[thread overview]
Message-ID: <20130627160057.GF2336@tucnak.redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1306271746331.26429@stedding.saclay.inria.fr>

On Thu, Jun 27, 2013 at 05:54:10PM +0200, Marc Glisse wrote:
> I don't really see why, as I am still calling c_build_vec_perm_expr
> in the same cases, just possibly not exactly with the same arguments
> (they don't go through build_non_dependent_expr, but Jason seemed to
> imply that it did not matter since we don't look too deep through
> the arguments).

I guess you're right.  If the c_* routine doesn't mind C++ specific trees
and just cares about their types and pt.c then instantiates it, then it is
fine.

	Jakub

  reply	other threads:[~2013-06-27 16:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-09 11:09 Marc Glisse
2013-06-26 14:20 ` Marc Glisse
2013-06-26 20:56 ` Jason Merrill
2013-06-27 11:59   ` Marc Glisse
2013-06-27 12:27     ` Jason Merrill
2013-06-27 15:29       ` Marc Glisse
2013-06-27 15:40         ` Jakub Jelinek
2013-06-27 15:55           ` Marc Glisse
2013-06-27 16:09             ` Jakub Jelinek [this message]
2013-06-27 16:10               ` Marc Glisse
2013-06-27 21:58                 ` Marc Glisse
2013-06-28  6:20     ` Jakub Jelinek
2013-06-28  8:48       ` Marc Glisse
2013-06-28 10:34         ` Marc Glisse

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=20130627160057.GF2336@tucnak.redhat.com \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@redhat.com \
    --cc=marc.glisse@inria.fr \
    /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).