From: Uros Bizjak <ubizjak@gmail.com>
To: "Senkevich, Andrew" <andrew.senkevich@intel.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"andrew.n.senkevich@gmail.com" <andrew.n.senkevich@gmail.com>
Subject: Re: [PATCH] Rename __builtin_ia32_kmov16 to __builtin_ia32_kmovw in gcc-{5,6}-branch
Date: Wed, 31 May 2017 15:33:00 -0000 [thread overview]
Message-ID: <CAFULd4bgywKyKe7KsF+xcDXmkcgsqjF0wk1cb_yOzfKW6QAAAQ@mail.gmail.com> (raw)
In-Reply-To: <D373487E0338A646909492FF43BA8BE356B56BA9@irsmsx110.ger.corp.intel.com>
On Wed, May 31, 2017 at 12:33 PM, Senkevich, Andrew
<andrew.senkevich@intel.com> wrote:
> Hi,
>
> attached patches are for renaming __builtin_ia32_kmov16 to __builtin_ia32_kmovw in GCC 5.* and 6.* branches since it was renamed in master.
> Bootstrapped and regtested on x86_64-linux-gnu.
>
> gcc/
> * config/i386/i386.c (__builtin_ia32_kmovw): Renamed from
> __builtin_ia32_kmov16 since it was renamed in master.
> * config/i386/avx512fintrin.h: Ditto.
>
> Are they Ok to commit?
Various undocumented builtins are considered internal, unpublished
interface, so IMO there is no need to backport their renames.
Uros.
next prev parent reply other threads:[~2017-05-31 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 10:34 Senkevich, Andrew
2017-05-31 15:33 ` Uros Bizjak [this message]
2017-06-02 8:39 ` 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=CAFULd4bgywKyKe7KsF+xcDXmkcgsqjF0wk1cb_yOzfKW6QAAAQ@mail.gmail.com \
--to=ubizjak@gmail.com \
--cc=andrew.n.senkevich@gmail.com \
--cc=andrew.senkevich@intel.com \
--cc=gcc-patches@gcc.gnu.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).