From: Ben Elliston <bje@redhat.com>
To: cgen@sources.redhat.com
Subject: signed ifields
Date: Mon, 02 Apr 2001 00:09:00 -0000 [thread overview]
Message-ID: <15048.9662.712500.564363@scooby.apac.redhat.com> (raw)
In-Reply-To: <15045.22228.305989.505250@scooby.apac.redhat.com>
I'm struggling to understand some aspects of CGEN's design with
respect to {signed,unsigned} quantities for instruction fields. I'm
unsure about why it makes sense to attribute "signedness" to what is
effectively a sequence of bits. Shouldn't the signedness be
attributed to operands (which it already can be)? It seems redundant
that both objects can be attributed as such.
I bring this up because some internal users of CGEN have been caught
by unintuitive behavior when using (dnf ..) to define their ifields
and then flagging their operands as signed, only to find that the
extraction code treats the underlying ifield as unsigned.
Comments?
Ben
parent reply other threads:[~2001-04-02 0:09 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <15045.22228.305989.505250@scooby.apac.redhat.com>]
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=15048.9662.712500.564363@scooby.apac.redhat.com \
--to=bje@redhat.com \
--cc=cgen@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).