From: David Miller <davem@davemloft.net>
To: ebotcazou@adacore.com
Cc: gcc@gcc.gnu.org, rth@redhat.com
Subject: Re: VIS2 pattern review
Date: Fri, 14 Oct 2011 06:06:00 -0000 [thread overview]
Message-ID: <20111013.214938.591570193816583158.davem@davemloft.net> (raw)
In-Reply-To: <201110140041.42467.ebotcazou@adacore.com>
From: Eric Botcazou <ebotcazou@adacore.com>
Date: Fri, 14 Oct 2011 00:41:42 +0200
>> Unfortunately, that would involve some ABI changes for the VIS
>> builtins. I'm trending towards considering just changing things
>> anyways since the VIS intrinsics were next to unusable beforehand.
>
> Could you elaborate? The calling conventions for vectors (like for the other
> classes) shouldn't depend on the mode but only on the type.
Right and as Richard said I can munge the modes during expansion of
existing builtins when needed.
next prev parent reply other threads:[~2011-10-14 1:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 12:29 Richard Henderson
2011-10-13 19:56 ` David Miller
2011-10-13 20:06 ` David Miller
2011-10-13 20:20 ` Richard Henderson
2011-10-13 22:46 ` David Miller
2011-10-13 22:53 ` Richard Henderson
2011-10-14 1:50 ` David Miller
2011-10-14 4:38 ` Eric Botcazou
2011-10-14 6:06 ` David Miller [this message]
2011-10-14 16:40 ` Eric Botcazou
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=20111013.214938.591570193816583158.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ebotcazou@adacore.com \
--cc=gcc@gcc.gnu.org \
--cc=rth@redhat.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).