From: Jan Beulich <jbeulich@suse.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH 0/5] x86/Intel: AVX512 syntax enhancements
Date: Wed, 25 May 2022 09:44:08 +0200 [thread overview]
Message-ID: <76748824-c662-b9db-a824-0e494c0a2986@suse.com> (raw)
In-Reply-To: <26c648e6-d76b-052e-6392-48265a859a7c@suse.com>
On 04.05.2022 13:44, Jan Beulich via Binutils wrote:
> As pointed out long ago already, what gas accepts and what objdump
> emits isn't in line with the SDM. Finally I also happened to find
> mention of this in MASM documentation [1]. This series extends (gas)
> and converts (objdump) respective support. As a nice side effect, a
> few hundred insn templates go away from the opcode table.
>
> 1: Intel: adjust representation of embedded broadcast
> 2: Intel: allow MASM representation of embedded broadcast
> 3: Intel: adjust representation of embedded rounding / SAE
> 4: re-work AVX512 embedded rounding / SAE
> 5: Intel: allow MASM representation of embedded rounding / SAE
I've now left this pending for 3 full weeks. Unless I hear back by
then I'm intending to commit this late this or early next week.
Regards, Jan
next prev parent reply other threads:[~2022-05-25 7:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 11:44 Jan Beulich
2022-05-04 11:57 ` [PATCH 1/5] x86/Intel: adjust representation of embedded broadcast Jan Beulich
2022-05-04 11:58 ` [PATCH 2/5] x86/Intel: allow MASM " Jan Beulich
2022-05-04 11:59 ` [PATCH 3/5] x86/Intel: adjust representation of embedded rounding / SAE Jan Beulich
2022-05-04 12:00 ` [PATCH 4/5] x86: re-work AVX512 " Jan Beulich
2022-05-04 12:01 ` [PATCH 5/5] x86/Intel: allow MASM representation of " Jan Beulich
2022-05-10 2:37 ` [PATCH 0/5] x86/Intel: AVX512 syntax enhancements Cui, Lili
2022-05-17 12:00 ` Jan Beulich
2022-05-18 3:15 ` Cui, Lili
2022-05-18 6:40 ` Jan Beulich
2022-05-18 15:07 ` H.J. Lu
2022-05-25 7:44 ` Jan Beulich [this message]
2022-05-26 14:48 ` H.J. Lu
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=76748824-c662-b9db-a824-0e494c0a2986@suse.com \
--to=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).