From: Jakub Jelinek <jakub@redhat.com>
To: Ira Rosen <ira.rosen@linaro.org>
Cc: Ramana Radhakrishnan <ramana.radhakrishnan@linaro.org>,
gcc-patches@gcc.gnu.org,
Patch Tracking <patches@linaro.org>
Subject: Re: [patch] Support vectorization of widening shifts
Date: Tue, 18 Oct 2011 10:53:00 -0000 [thread overview]
Message-ID: <20111018094343.GO2210@tyan-ft48-01.lab.bos.redhat.com> (raw)
In-Reply-To: <CAKSNEw7y7iteMsff1DvXagyXL4ZX6Sm9_3i7J9doWB2-fnSe+w@mail.gmail.com>
On Tue, Oct 18, 2011 at 11:39:22AM +0200, Ira Rosen wrote:
> On 2 October 2011 10:30, Ira Rosen <ira.rosen@linaro.org> wrote:
> > On 29 September 2011 17:30, Ramana Radhakrishnan
> > <ramana.radhakrishnan@linaro.org> wrote:
> >> On 19 September 2011 08:54, Ira Rosen <ira.rosen@linaro.org> wrote:
> >>
> >>>
> >>> Bootstrapped on powerpc64-suse-linux, tested on powerpc64-suse-linux
> >>> and arm-linux-gnueabi
> >>> OK for mainline?
> >>
> >> Sorry I missed this patch. Is there any reason why we need unspecs in
> >> this case ? Can't this be represented by subregs and zero/ sign
> >> extensions in RTL without the UNSPECs ?
>
> I committed the attached patch with Ramana's solution for testing
> +/* Detect widening shift pattern:
>
> + type a_t;
> + TYPE a_T, res_T;
> +
> + S1 a_t = ;
> + S2 a_T = (TYPE) a_t;
> + S3 res_T = a_T << CONST;
> +
> + where type 'TYPE' is at least double the size of type 'type'.
> +
> + Also detect unsgigned cases:
unsigned
Jakub
next prev parent reply other threads:[~2011-10-18 9:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-19 8:26 Ira Rosen
2011-09-26 14:40 ` Richard Guenther
2011-09-27 7:40 ` Ira Rosen
2011-09-27 13:17 ` Richard Guenther
2011-09-29 15:42 ` Ramana Radhakrishnan
2011-10-02 8:31 ` Ira Rosen
2011-10-18 10:48 ` Ira Rosen
2011-10-18 10:53 ` Jakub Jelinek [this message]
2011-10-18 11:33 ` Ira Rosen
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=20111018094343.GO2210@tyan-ft48-01.lab.bos.redhat.com \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ira.rosen@linaro.org \
--cc=patches@linaro.org \
--cc=ramana.radhakrishnan@linaro.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).