From: Doug Evans <dje@sebabeach.org>
To: Dave Brolley <brolley@redhat.com>
Cc: cgen@sourceware.org
Subject: Re: CGEN_BITSET
Date: Mon, 22 Jun 2009 16:19:00 -0000 [thread overview]
Message-ID: <4A3FAF00.7040701@sebabeach.org> (raw)
In-Reply-To: <4A3FAA79.3050203@redhat.com>
Hi. Thanks.
More than 32 ISAs? Yikes!
Going forward, we could add a vbitset attribute kind (or some such), or
we could convert all bitsets to use CGEN_BITSET. I guess I'm leaning
toward the latter, but I can imagine situations where one would rather
just have an unsigned int.
Dave Brolley wrote:
> Hi Doug,
>
> The mep port required an inderminate and configurable number of ISA's
> to be possible, so we needed something that could represent an
> unspecified number of bits (more then 32 or 64 possibly) in a mask.
> The intent was not to treat isa specially. It just turned out to be
> the first bit mask to require this treatment.
>
> CGEN_BITSET is simply a bit mask represented by character strings as
> opposed to integers.
>
> Dave
>
> Doug Evans wrote:
>> Treating "isa" specially is a bit of a hack. What's the story behind
>> CGEN_BITSET?
>>
>> (define (gen-attr-type attr)
>> (if (string=? (string-downcase (gen-sym attr)) "isa")
>> "CGEN_BITSET"
>> (case (attr-kind attr)
>> ((boolean) "int")
>> ((bitset) "unsigned int")
>> ((integer) "int")
>> ((enum) (string-append "enum " (string-downcase (gen-sym
>> attr)) "_attr"))
>> ))
>> )
>>
prev parent reply other threads:[~2009-06-22 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-20 22:39 CGEN_BITSET Doug Evans
2009-06-22 16:00 ` CGEN_BITSET Dave Brolley
2009-06-22 16:19 ` Doug Evans [this message]
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=4A3FAF00.7040701@sebabeach.org \
--to=dje@sebabeach.org \
--cc=brolley@redhat.com \
--cc=cgen@sourceware.org \
/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).