From: Hongtao Liu <crazylht@gmail.com>
To: LiYancheng <yancheng.li@foxmail.com>
Cc: Andrew Pinski <pinskia@gmail.com>, Jan Hubicka <hubicka@ucw.cz>,
GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: [Intel SPR] Progress of GCC support for Intel SPR features
Date: Mon, 7 Feb 2022 14:35:30 +0800 [thread overview]
Message-ID: <CAMZc-bwMUj53a2Nwt4Lqck5fX67vr0XGm=xq2OqjuJqONBOMbQ@mail.gmail.com> (raw)
In-Reply-To: <tencent_1C1FE75BE9320579CCF25A6EBCAA51211706@qq.com>
On Mon, Feb 7, 2022 at 11:16 AM LiYancheng via Gcc <gcc@gcc.gnu.org> wrote:
>
>
> On 2022/2/7 10:03, Andrew Pinski wrote:
> > On Sun, Feb 6, 2022 at 5:59 PM LiYancheng via Gcc <gcc@gcc.gnu.org> wrote:
> >> Hello everyone!
> >>
> >> I have some questions to ask:
> >>
> >> 1. How does GCC support Sapphrie Rapids CPU now?
> >>
> >> 2. Does GCC 11 fully support all the features of SPR?
> >> From the release note, it seems that 5g ISA (fp16)/hfni is
> >> not supported yet.
> > It will be included in GCC 12 which should be released in less than 4 months.
> Thank you for your reply！
> >> 3. What is the simulation tool used by GCC to verify SPR characteristics?
> >> Is it open source?
> > Intel is doing the patching to GCC and binutils so I suspect they
> > verify using their internal tools and I highly doubt it is free
> > source.
> >
> >
> > Thanks,
> > Andrew Pinski
> >
> Any suggestions from Intel?
>
You can use Intel SDE(software-development-emulator)
refer to https://www.intel.com/content/www/us/en/developer/articles/tool/software-development-emulator.html.
And please use GCC12(main trunk, not released yet), and binutils
2.38(main trunk, not released yet).
> Thanks!
>
> yancheng
>
> >> Thanks for all the help,
> >>
> >> yancheng
> >>
--
BR,
Hongtao
prev parent reply other threads:[~2022-02-07 6:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4652ef74-3f2d-f04c-d560-de89ff37013c@foxmail.com>
2022-02-07 1:57 ` LiYancheng
2022-02-07 2:03 ` Andrew Pinski
2022-02-07 3:15 ` LiYancheng
2022-02-07 6:35 ` 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-bwMUj53a2Nwt4Lqck5fX67vr0XGm=xq2OqjuJqONBOMbQ@mail.gmail.com' \
--to=crazylht@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=pinskia@gmail.com \
--cc=yancheng.li@foxmail.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).