public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "H. J. Lu" <hjl@lucon.org>
To: binutils@sources.redhat.com
Subject: RFC: Adding more bits to opcode_modifier and operand_types in x86 assembler
Date: Thu, 06 Jul 2006 16:29:00 -0000	[thread overview]
Message-ID: <20060706162925.GA17536@lucon.org> (raw)

I found a need to add more bits to opcode_modifier and operand_types in
template in x86 assembler. They are currently 32bits and there are no
unused bits left. I am considering 2 choices:

1. Change them to unsigned long long.
   Pros: Other 32bit ports have used long long. Minimal changes are
   required.
   Cons: Compiler has to support long long. We may run out bits later.
2. Change them to use bitfields.
   Pros: More extensible. No long long support is needed.
   Cons: Need significant changes. It isn't easy to initialize 1000+
   structures with 100+ fields. Designated initializers help. But it
   needs C99 support.

Both choices will work with the current gcc. I prefer bitfields if
designated initializers can be used. It looks that there are more
compilers with long long support than with designated initializer
support. I'd like to use unsigned long long first and change to
bitfields later when designated initializer support can be required
by binutils.

Any comments?


H.J.

             reply	other threads:[~2006-07-06 16:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-06 16:29 H. J. Lu [this message]
2006-07-10  8:58 ` Alan Modra

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=20060706162925.GA17536@lucon.org \
    --to=hjl@lucon.org \
    --cc=binutils@sources.redhat.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).