From: "H.J. Lu" <hjl.tools@gmail.com>
To: Kirill Yukhin <kirill.yukhin@gmail.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
gcc-patches List <gcc-patches@gcc.gnu.org>,
Uros Bizjak <ubizjak@gmail.com>
Subject: Re: [PATCH, i386 tests] New tests to check vectorization for AVX2 insns.
Date: Tue, 18 Oct 2011 16:49:00 -0000 [thread overview]
Message-ID: <CAMe9rOotUfWLnHTOpT2nDji6oTKRJjX2MgMSR5uJ_vtTpsFr7g@mail.gmail.com> (raw)
In-Reply-To: <CAGs3RfsPm31_acosrVYcz0XrXoimXe__AXqdyz0Jn7Sr6E6BQA@mail.gmail.com>
On Mon, Oct 17, 2011 at 7:49 AM, Kirill Yukhin <kirill.yukhin@gmail.com> wrote:
> Thanks, guys, could anybody please commit that?
>
I checked it in for you.
--
H.J.
next prev parent reply other threads:[~2011-10-18 15:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 11:54 Kirill Yukhin
2011-10-14 12:10 ` Jakub Jelinek
2011-10-14 14:05 ` Kirill Yukhin
2011-10-14 14:44 ` Jakub Jelinek
2011-10-17 14:39 ` Kirill Yukhin
2011-10-17 14:49 ` Jakub Jelinek
2011-10-17 16:03 ` Kirill Yukhin
2011-10-18 16:49 ` H.J. Lu [this message]
2011-10-18 16:54 ` Kirill Yukhin
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=CAMe9rOotUfWLnHTOpT2nDji6oTKRJjX2MgMSR5uJ_vtTpsFr7g@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=kirill.yukhin@gmail.com \
--cc=ubizjak@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).