public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: Richard Biener <rguenther@suse.de>,
	GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] i386: Move Intel intrinsics head files to <immintrin.h>
Date: Sun, 20 Jan 2019 18:18:00 -0000	[thread overview]
Message-ID: <CAMe9rOqVsQkJ5sQT2eMn98_qLuipD--yMS3YJJNEfce7Z6TbGA@mail.gmail.com> (raw)
In-Reply-To: <CAFULd4ZoqFy2t9O7Pc4M9_wdu_a-oeiyZX5K5ORVQu2B-e5FGg@mail.gmail.com>

On Sun, Jan 20, 2019 at 10:12 AM Uros Bizjak <ubizjak@gmail.com> wrote:
>
> On Sun, Jan 20, 2019 at 7:09 PM Uros Bizjak <ubizjak@gmail.com> wrote:
> >
> > On Sun, Jan 20, 2019 at 4:11 PM H.J. Lu <hjl.tools@gmail.com> wrote:
> > >
> > > On Sun, Jan 20, 2019 at 4:03 AM Uros Bizjak <ubizjak@gmail.com> wrote:
> > > >
> > > > On 1/19/19, H.J. Lu <hjl.tools@gmail.com> wrote:
> > > > > According to Intel Intrinsics Guide:
> > > > >
> > > > > https://software.intel.com/sites/landingpage/IntrinsicsGuide/
> > > > >
> > > > > Intel intrinsics should be available by including <immintrin.h>.  This
> > > > > patch moves remaining Intel intrinsics head files from <x86intrin.h> to
> > > > > <immintrin.h>.
> > > >
> > > > I can't find the quoted requirement in the provided link.
> > >
> > > That is an interactive website.  If you type in "_xgetbv" and click on it,
> > > you will get
> > >
> > > Synopsis
> > >
> > > unsigned __int64 _xgetbv (unsigned int a)
> > > #include <immintrin.h>
> > > Instruction: xgetbv
> > > CPUID Flags: XSAVE
> > >
> > > Description
> > >
> > > Copy up to 64-bits from the value of the extended control register
> > > (XCR) specified by a into dst. Currently only XFEATURE_ENABLED_MASK
> > > XCR is supported.
> > >
> > > Operation
> > >
> > > dst[63:0] := XCR[a]
> >
> > Ah, thanks for the hint. LGTM, but still needs RM approval.
>
> I wonder, what is/was the purpose of x86intrin.h, considering that
> everything can be included from immintrin.h?

Some intrinsics aren't covered by Intel Intrinsics Guide, like AMD
specific ones.

-- 
H.J.

  reply	other threads:[~2019-01-20 18:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-19 16:02 H.J. Lu
2019-01-20 12:03 ` Uros Bizjak
2019-01-20 15:11   ` H.J. Lu
2019-01-20 18:09     ` Uros Bizjak
2019-01-20 18:12       ` Uros Bizjak
2019-01-20 18:18         ` H.J. Lu [this message]
2019-01-21  8:04       ` Richard Biener

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=CAMe9rOqVsQkJ5sQT2eMn98_qLuipD--yMS3YJJNEfce7Z6TbGA@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rguenther@suse.de \
    --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).