From: Jan Beulich <jbeulich@suse.com>
To: Binutils <binutils@sourceware.org>
Cc: "H.J. Lu" <hjl.tools@gmail.com>
Subject: [PATCH 0/4] x86: fold a number of VEX and EVEX templates
Date: Fri, 15 Sep 2023 10:46:29 +0200 [thread overview]
Message-ID: <0690c179-ac98-d127-5ff4-b5abb725b6ae@suse.com> (raw)
The last two patches are explicitly RFC, for having a possibly unwanted
side effect.
1: fold certain VEX and EVEX templates
2: fold VAES/VPCLMULQDQ VEX and EVEX templates
3: fold FMA VEX and EVEX templates
4: fold F16C VEX and EVEX templates
Jan
next reply other threads:[~2023-09-15 8:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 8:46 Jan Beulich [this message]
2023-09-15 8:47 ` [PATCH 1/4] x86: fold certain " Jan Beulich
2023-09-15 8:48 ` [PATCH 2/4] x86: fold VAES/VPCLMULQDQ " Jan Beulich
2023-09-15 8:48 ` [PATCH RFC 3/4] x86: fold FMA " Jan Beulich
2023-09-15 8:49 ` [PATCH RFC 4/4] x86: fold F16C " Jan Beulich
2023-09-18 1:58 ` [PATCH 0/4] x86: fold a number of " Hongtao Liu
2023-09-18 5:47 ` Cui, Lili
2023-09-18 9:38 ` Jan Beulich
2023-09-18 11:18 ` Cui, Lili
2023-09-18 11:49 ` Jan Beulich
2023-09-18 12:03 ` Cui, Lili
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=0690c179-ac98-d127-5ff4-b5abb725b6ae@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).