From: Uros Bizjak <ubizjak@gmail.com>
To: Marc Glisse <marc.glisse@inria.fr>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [x86, 7/n] Replace builtins with vector extensions
Date: Tue, 11 Nov 2014 13:19:00 -0000 [thread overview]
Message-ID: <CAFULd4aGTvrkfBO=7zm8y=uvqHPcXV7TpP=EgUrDcvYf2h9-JQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1411111231500.11887@stedding.saclay.inria.fr>
On Tue, Nov 11, 2014 at 12:35 PM, Marc Glisse <marc.glisse@inria.fr> wrote:
> last patch, extending == and > to size 256. Regtested as usual.
>
> Is the branch ready to be merged into trunk?
>
> 2014-11-10 Marc Glisse <marc.glisse@inria.fr>
>
> * config/i386/emmintrin.h (_mm_cmpeq_epi8, _mm_cmpeq_epi16,
> _mm_cmpeq_epi32, _mm_cmplt_epi8, _mm_cmplt_epi16, _mm_cmplt_epi32,
> _mm_cmpgt_epi8, _mm_cmpgt_epi16, _mm_cmpgt_epi32): Use vector
> extensions instead of builtins.
> * config/i386/smmintrin.h (_mm_cmpeq_epi64, _mm_cmpgt_epi64):
> Likewise.
OK.
Please post the complete ChangeLog and complete patch for a review and merge.
Thanks,
Uros.
prev parent reply other threads:[~2014-11-11 13:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 11:36 Marc Glisse
2014-11-11 13:19 ` Uros Bizjak [this message]
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='CAFULd4aGTvrkfBO=7zm8y=uvqHPcXV7TpP=EgUrDcvYf2h9-JQ@mail.gmail.com' \
--to=ubizjak@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--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).