public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH] x86: fold special-operand insn attributes into a single enum
Date: Fri, 11 Nov 2022 09:00:31 +0100	[thread overview]
Message-ID: <2a971dfe-00b6-856b-5f3b-8a1cd7dc78c6@suse.com> (raw)
In-Reply-To: <CAMe9rOrCEY2==LAvr+6N76JgTivsy46EVtpJawOzmxZS-aKhfw@mail.gmail.com>

On 10.11.2022 18:38, H.J. Lu wrote:
> On Thu, Nov 10, 2022 at 5:45 AM Jan Beulich <jbeulich@suse.com> wrote:
>>
>> Attributes which aren't used together in any single insn template can be
>> converted from individual booleans to a single enum, as was done for a few
>> other attributes before. This is more space efficient. Collect together
>> all attributes which express special operand constraints (and which fit
>> the criteria for folding).
> 
> These assumptions may not be all true for future new instructions.

It seems pretty unlikely to me that any of these assumptions would break.
If one does, converting back to an individual bit is an easy option. I
think this minor risk is far outweighed by the benefits of the change. We
really have still some ways to go to reach reasonable data representation
within the generated opcode table (and of course also in the source table,
but that's an orthogonal direction of work, where I also have further
changes pending).

Jan

  reply	other threads:[~2022-11-11  8:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10 13:45 Jan Beulich
2022-11-10 17:38 ` H.J. Lu
2022-11-11  8:00   ` Jan Beulich [this message]
2022-11-11  8:22     ` Jan Beulich
2022-11-11 19:48       ` H.J. Lu
2022-11-14  1:38         ` Jiang, Haochen
2022-11-14 15:58 ` 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=2a971dfe-00b6-856b-5f3b-8a1cd7dc78c6@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).