From: "Jiang, Haochen" <haochen.jiang@intel.com>
To: "Beulich, Jan" <JBeulich@suse.com>
Cc: "hjl.tools@gmail.com" <hjl.tools@gmail.com>,
"binutils@sourceware.org" <binutils@sourceware.org>
Subject: RE: [PATCH] x86: Remove the restriction for size of the mask register in AVX10
Date: Mon, 18 Dec 2023 03:18:08 +0000 [thread overview]
Message-ID: <SA1PR11MB5946AE633FEB09AFD859B7B5EC90A@SA1PR11MB5946.namprd11.prod.outlook.com> (raw)
In-Reply-To: <SA1PR11MB5946B396267EE24789309D93EC90A@SA1PR11MB5946.namprd11.prod.outlook.com>
> -----Original Message-----
> From: Jiang, Haochen
> Sent: Monday, December 18, 2023 10:58 AM
> To: Jan Beulich <jbeulich@suse.com>
> Cc: hjl.tools@gmail.com; binutils@sourceware.org
> Subject: RE: [PATCH] x86: Remove the restriction for size of the mask register
> in AVX10
>
> > Well, if no template uses it anymore, then the attribute can hardly still
> > be needed for anything. From my checking, all other affected templates
> > are restricted based on their EVex<N> attributes instead. And my
> > recollection also is that I introduced the attribute solely for the
> > purpose of the opmask insns.
>
> I suppose we could remove that if that is the case and I am finding a proper
> way since we need to keep some diagnostic messages for the options.
Oh I got some misunderstandings previously here, I suppose we are only removing
the Vsz in opcode_modifier but not all of them right? If that is true, I suppose my
current v2 patch is ok and I will send out that.
Thx,
Haochen
>
> Thx,
> Haochen
>
> >
> > Yet of course if internally you have indications that the attribute is
> > going to be needed for something again (within foreseeable future), then
> > we might better keep it.
> >
> > Jan
prev parent reply other threads:[~2023-12-18 3:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 2:23 Haochen Jiang
2023-12-15 7:51 ` Jan Beulich
2023-12-15 8:06 ` Jiang, Haochen
2023-12-15 8:15 ` Jan Beulich
2023-12-18 2:58 ` Jiang, Haochen
2023-12-18 3:18 ` 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=SA1PR11MB5946AE633FEB09AFD859B7B5EC90A@SA1PR11MB5946.namprd11.prod.outlook.com \
--to=haochen.jiang@intel.com \
--cc=JBeulich@suse.com \
--cc=binutils@sourceware.org \
--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).