From: "Kai Henningsen" <kai.extern@googlemail.com>
To: cgen@sources.redhat.com
Subject: Some CGEN problems
Date: Mon, 21 Apr 2008 08:12:00 -0000 [thread overview]
Message-ID: <7af24c80804191023q318f850do9db5458352163d19@mail.gmail.com> (raw)
I'm playing with CGEN for a virtual cpu.
Maybe the largest problem (after the rather sparse documentation) is
that the pmacro system seems to be much weaker than GCC's iterator
system.
I've yet to figure out a way to iterate over two variables (such as
"integer opcodes" and "modes for integer opcodes"), or a way to handle
what GCC does with iterator attributes (such as the mapping from RTL
operands to opcode names). Right now, the best way I can think of is
to generate CGEN input with a Perl script ... but surely the whole
point of CGEN is that I shouldn't need that?!
This (and the growing list of stuff that I find that CGEN doesn't even
try to handle) makes me wonder if it might be easier to not use CGEN.
Of course, binutils documentation isn't any better. I thought GCC
documentation was sparse, but compared with these two, it's positively
encyclopedic!
next reply other threads:[~2008-04-19 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 8:12 Kai Henningsen [this message]
2008-04-21 19:06 ` Frank Ch. Eigler
2008-04-21 19:36 ` Kai Henningsen
2008-04-22 17:18 ` Frank Ch. Eigler
2008-04-26 18:37 ` Jim Blandy
2008-06-01 14:14 ` Kai Henningsen
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=7af24c80804191023q318f850do9db5458352163d19@mail.gmail.com \
--to=kai.extern@googlemail.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).