From: Doug Evans <dje@sebabeach.org>
To: cgen@sourceware.org
Subject: bitset attribute handling reorg
Date: Mon, 26 Oct 2009 01:00:00 -0000 [thread overview]
Message-ID: <20091026010050.9B0226E3D5@sebabeach.org> (raw)
Hi.
I changed how the bitset attribute is represented.
Internally it's no longer "a,b,c" and is instead (a b c).
Externally one can still use "a,b,c" in description files
but the preferred way is now (a b c).
a,b,c (i.e. a symbol, no quotes) is still supported but it is deprecated,
a,b,c is not a valid R6RS symbol.
Tested by regenerating the world, no changes.
[world: opcodes, sim, sid, intrinsics, docs]
2009-10-25 Doug Evans <dje@sebabeach.org>
Record bitset attributes internally as a list.
Record rtx attribute values internally as ((rtx-expr)).
* attr.scm (bitset-attr?): Delete, unused.
(<bitset-attribute> parse-value): Rewrite.
(/attr-parse): Rewrite bitset default value processing.
(/attr-read): Pick out values of scalar attributes to distinguish
them from bitset values which are a list.
Fix spelling errors for processing of default values.
Handle string attributes.
(bitset-attr->list): Delete, all callers updated.
(/bitset-attr->charmask): Renamed from bitset-attr->charmask.
All callers updated.
(atlist-source-form): Rewrite.
* hardware.scm (<hardware-base> 'get-isas): Update recognition
of all isas.
(hardware-builtin!): Update spec of ISA attribute, (ISA foo,bar)
-> (ISA foo bar).
* intrinsics.scm (target:belongs-to-group?): Update, bitset attribute
values are now lists.
* mach.scm (def-isa-attr!): Update, bitset attribute values,
including the default, are now lists.
(all-isas-attr-value): Result is now a list.
* doc/rtl.texi: Clean up pass over attribute docs.
Change internal representation of rtx attribute values.
* attr.scm (/attr-val-is-rtx?): New function.
(attr-value): Call it.
(atlist-attr-value-no-default, attr-lookup-default): Ditto.
(/attr-parse): Use /attr-val-is-rtx? to detect rtx values.
Disallow rtx values for bitset attributes.
(/attr-read): Record rtx in default value as ((rtx-expr)).
(/attr-eval): Update.
reply other threads:[~2009-10-26 1:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20091026010050.9B0226E3D5@sebabeach.org \
--to=dje@sebabeach.org \
--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).