From: Jan Beulich <jbeulich@suse.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Binutils <binutils@sourceware.org>
Subject: x86: limiting the use of No_*Suf
Date: Fri, 12 Aug 2022 11:30:36 +0200 [thread overview]
Message-ID: <12efdcf2-82f2-7683-7f55-3fac382326f9@suse.com> (raw)
H.J.,
since you didn't like "x86: imply all No_*Suf when none is set in a
template" I've been thinking of other ways to limit the excessive use
of these attributes. One observation is that templates with IsPrefix,
Broadcast, or Masking set always have all No_<x>Suf also set.
Therefore the latter could be dropped from those templates (improving
readability), compensated by
1) a respective adjustment to match_template(), or
2) a change to i386-gen.c, or
3) respective pre-processor macros.
Do you have any opinion on the general direction of this and, if in
favor, any preference for one of the three options?
Jan
next reply other threads:[~2022-08-12 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 9:30 Jan Beulich [this message]
2022-08-12 13:18 ` Jan Beulich
2022-08-15 18:10 ` 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=12efdcf2-82f2-7683-7f55-3fac382326f9@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).