From: "Jiang, Haochen" <haochen.jiang@intel.com>
To: Richard Biener <richard.guenther@gmail.com>,
Florian Weimer <fweimer@redhat.com>
Cc: Hongtao Liu <crazylht@gmail.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"Liu, Hongtao" <hongtao.liu@intel.com>,
"ubizjak@gmail.com" <ubizjak@gmail.com>
Subject: RE: [RFC] Intel AVX10.1 Compiler Design and Support
Date: Wed, 13 Dec 2023 02:12:36 +0000 [thread overview]
Message-ID: <SA1PR11MB594661C742CC414D54B391A2EC8DA@SA1PR11MB5946.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAFiYyc2_VxNnSnV4J3BxCRc6Q=RQACgFwNVJH-aYkjVZqyF7bQ@mail.gmail.com>
> > On the other hand, a new EVEX-capable level might bring earlier adoption
> > of EVEX capabilities to AMD CPUs, which still should be an improvement
> > over AVX2. This could benefit AMD as well. So I would really like to
> > see some AMD feedback here.
> >
> > There's also the matter that time scales for EVEX adoption are so long
> > that by then, Intel CPUs may end up supporting and preferring 512 bit
> > vectors again.
>
> True, there isn't even widespread VEX adoption yet ... and now there's
> APX as the next best thing to target.
>
> That said, my main point was that x86-64-v4 is "broken" as it appears
> as a dead end - AVX512 is no more, the future is AVX10, but yet we have
> to define x86-64-v5 as something that includes x86-64-v4.
>
> So, can we un-do x86-64-v4?
As far as I have heard, x86-64-v4 is rarely used. There should be a small
chance to un-do that and not to break too many things. But I am not sure.
Thx,
Haochen
>
> Richard.
>
> > Thanks,
> > Florian
> >
prev parent reply other threads:[~2023-12-13 2:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 1:41 Haochen Jiang
2023-11-10 1:41 ` [PATCH] Initial support for AVX10.1 Haochen Jiang
2023-11-20 6:34 ` Hongtao Liu
2023-11-10 10:15 ` [RFC] Intel AVX10.1 Compiler Design and Support Richard Biener
2023-11-13 7:07 ` Hongtao Liu
2023-11-13 11:25 ` Richard Biener
2023-11-14 2:40 ` Hongtao Liu
2023-11-14 6:25 ` Jiang, Haochen
2023-12-12 9:05 ` Florian Weimer
2023-12-12 12:14 ` Richard Biener
2023-12-13 2:12 ` Jiang, Haochen [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=SA1PR11MB594661C742CC414D54B391A2EC8DA@SA1PR11MB5946.namprd11.prod.outlook.com \
--to=haochen.jiang@intel.com \
--cc=crazylht@gmail.com \
--cc=fweimer@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hongtao.liu@intel.com \
--cc=richard.guenther@gmail.com \
--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).