From: Jan Beulich <jbeulich@suse.com>
To: "Jiang, Haochen" <haochen.jiang@intel.com>,
Binutils <binutils@sourceware.org>
Cc: "H.J. Lu" <hjl.tools@gmail.com>
Subject: Re: [PATCH v2 3/3] x86: support AVX10.1 vector size restrictions
Date: Tue, 5 Sep 2023 10:40:52 +0200 [thread overview]
Message-ID: <4a718396-93cf-be5a-ca43-a338ce703697@suse.com> (raw)
In-Reply-To: <SA1PR11MB59462F4F2B084028380CB7ACECE8A@SA1PR11MB5946.namprd11.prod.outlook.com>
On 05.09.2023 10:11, Jiang, Haochen wrote:
>> Recognize "/<number>" suffixes on both -march=+avx10.1 and the
>> corresponding .arch directive, setting an upper bound on the vector size
>> that insns may use. Such a restriction can be reset by setting a new base
>> architecture, by using a suffix-less form, by disabling AVX10, or by
>> enabling any other VEX/EVEX-based vector extension.
>
> Currently in GCC community, they are asking for an option -m[no-]evex512
> to enable/disable 512 bit register and 64 bit mask register. I will add a similar
> option in binutils afterwards.
>
> Also, they are not willing to introduce actual -mavx10.1-256/512. Therefore,
> it might become a little problematic to introduce them in binutils only.
I don't see a problem with compiler and assembler supporting somewhat
diverging options. In fact we already have examples, like -m64 vs --64.
> But since there will be finally -mavx10.2-256/512, the current code change
> for attribute is always ok.
Good.
Jan
prev parent reply other threads:[~2023-09-05 8:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 7:49 [PATCH v2 0/3] x86: AVX10.1 (alternative attempt) Jan Beulich
2023-09-05 7:51 ` [PATCH v2 1/3] x86: make AES/PCMULQDQ respectively prereqs of VAES/VPCMULQDQ Jan Beulich
2023-09-05 7:52 ` [PATCH v2 2/3] x86: support AVX10.1/512 Jan Beulich
2023-09-05 8:00 ` Jiang, Haochen
2023-09-05 8:04 ` Jan Beulich
2023-09-05 8:13 ` Jiang, Haochen
2023-09-05 7:53 ` [PATCH v2 3/3] x86: support AVX10.1 vector size restrictions Jan Beulich
2023-09-05 8:11 ` Jiang, Haochen
2023-09-05 8:40 ` Jan Beulich [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=4a718396-93cf-be5a-ca43-a338ce703697@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=haochen.jiang@intel.com \
--cc=hjl.tools@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).