From: "Koval, Julia" <julia.koval@intel.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: Kirill Yukhin <kirill.yukhin@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: RE: [PATCH][i386,AVX] Enable VBMI2 support [5/7]
Date: Tue, 12 Dec 2017 09:05:00 -0000 [thread overview]
Message-ID: <4E89A029A0F8D443B436A5167BA3C53F8A452E4C@IRSMSX151.ger.corp.intel.com> (raw)
In-Reply-To: <alpine.LSU.2.21.1712091447420.2983@anthias.pfeifer.com>
Looks good. How to put it there(sorry, noob question)?
Thanks,
Julia
> -----Original Message-----
> From: Gerald Pfeifer [mailto:gerald@pfeifer.com]
> Sent: Saturday, December 09, 2017 2:49 PM
> To: Koval, Julia <julia.koval@intel.com>
> Cc: Kirill Yukhin <kirill.yukhin@gmail.com>; GCC Patches <gcc-
> patches@gcc.gnu.org>
> Subject: RE: [PATCH][i386,AVX] Enable VBMI2 support [5/7]
>
> Hi Julia,
>
> On Mon, 4 Dec 2017, Koval, Julia wrote:
> > Do you think it is ok to copypaste it from GCC-6?
>
> you mean copy, past, and adjust? Yes, that should work.
>
> > GCC now supports the Intel CPU, named Cannonlake through
> > -march=cannonlake. The switch enables the following ISA extensions:
> > AVX512VBMI, AVX512IFMA, SHA.
> > GCC now supports the Intel CPU, named and Icelake through
> > -march=icelake. The switch enables the following ISA extensions:
> > AVX512VNNI, GFNI, VAES, AVX512VBMI2, VPCLMULQDQ, AVX512BITALG,
> RDPID,
> > AVX512VPOPCNTDQ.
>
> No comma before "named".
>
> <code>-march=...</code>.
>
> And perhaps "enables the AVX..., AVX...,and... ISA extensions"?
>
> Gerald
next prev parent reply other threads:[~2017-12-12 9:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 10:05 Koval, Julia
2017-12-03 17:51 ` Gerald Pfeifer
2017-12-04 7:19 ` Koval, Julia
2017-12-09 13:49 ` Gerald Pfeifer
2017-12-12 9:05 ` Koval, Julia [this message]
2017-12-12 10:34 ` Gerald Pfeifer
2017-12-12 17:06 ` Koval, Julia
2017-12-12 22:18 ` Gerald Pfeifer
2017-10-24 10:16 Koval, Julia
2017-11-28 18:09 ` 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=4E89A029A0F8D443B436A5167BA3C53F8A452E4C@IRSMSX151.ger.corp.intel.com \
--to=julia.koval@intel.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=kirill.yukhin@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).