From: Hongtao Liu <crazylht@gmail.com>
To: Jeff Law <law@redhat.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Split X86_TUNE_AVX128_OPTIMAL into X86_TUNE_AVX256_SPLIT_REGS and X86_TUNE_AVX128_OPTIMAL
Date: Mon, 18 Nov 2019 07:31:00 -0000 [thread overview]
Message-ID: <CAMZc-bwRPtpfz5zCSDRVn7gV4Ni37xVAbm5Z8aHvqNzf2A0UHg@mail.gmail.com> (raw)
In-Reply-To: <e4256bf0-7b04-f816-2b64-b66f08188729@redhat.com>
On Sat, Nov 16, 2019 at 7:27 AM Jeff Law <law@redhat.com> wrote:
>
> On 11/14/19 5:21 AM, Richard Biener wrote:
> > On Tue, Nov 12, 2019 at 11:35 AM Hongtao Liu <crazylht@gmail.com> wrote:
> >>
> >> Hi:
> >> As mentioned in https://gcc.gnu.org/ml/gcc-patches/2019-11/msg00832.html
> >>> So yes, it's poorly named. A preparatory patch to clean this up
> >>> (and maybe split it into TARGET_AVX256_SPLIT_REGS and TARGET_AVX128_OPTIMAL)
> >>> would be nice.
> >>
> >> Bootstrap and regression test for i386 backend is ok.
> >> Ok for trunk?
> >
> > It looks OK to me, please let x86 maintainers a day to comment, otherwise OK
> I think this fine to go in now. Uros largely leaves the AVX bits to others.
Committed, thanks.
>
> jeff
>
--
BR,
Hongtao
prev parent reply other threads:[~2019-11-18 2:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 10:38 Hongtao Liu
2019-11-14 12:22 ` Richard Biener
2019-11-15 23:30 ` Jeff Law
2019-11-18 7:31 ` Hongtao Liu [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=CAMZc-bwRPtpfz5zCSDRVn7gV4Ni37xVAbm5Z8aHvqNzf2A0UHg@mail.gmail.com \
--to=crazylht@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=richard.guenther@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).