From: Doug Evans <dje@sebabeach.org>
To: cgen@sourceware.org
Subject: [commit] map each sformat to only one iformat
Date: Sat, 13 Feb 2010 04:36:00 -0000 [thread overview]
Message-ID: <20100213043646.4CB706E3DC@sebabeach.org> (raw)
A minor simplification.
It results in only a few more otherwise redundant sformats.
2010-02-12 Doug Evans <dje@sebabeach.org>
* iformat.scm (/sfmt-search-key): Use iformat key instead of list
of ifields.
Index: iformat.scm
===================================================================
RCS file: /cvs/src/src/cgen/iformat.scm,v
retrieving revision 1.17
diff -u -p -r1.17 iformat.scm
--- iformat.scm 13 Feb 2010 03:39:15 -0000 1.17
+++ iformat.scm 13 Feb 2010 04:34:05 -0000
@@ -284,11 +284,11 @@
")")))
)
(list
+ ;; Use the iformat key so that each sformat maps to only one iformat.
+ (if (= (length sorted-used-iflds) 0)
+ "no-used-ifields"
+ (ifmt-key (insn-ifmt insn)))
cti?
- (insn-length insn)
- (string-map (lambda (ifld)
- (string-append " (" (obj:str-name ifld) " " (ifld-ilk ifld) ")"))
- sorted-used-iflds)
(string-map op-key
sem-in-ops)
(string-map op-key
reply other threads:[~2010-02-13 4:36 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=20100213043646.4CB706E3DC@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).