From: "Kai Henningsen" <kai.extern@googlemail.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: cgen@sources.redhat.com
Subject: Re: Some CGEN problems
Date: Mon, 21 Apr 2008 19:36:00 -0000 [thread overview]
Message-ID: <7af24c80804211206x6e0f505fo1748b3af85a6d397@mail.gmail.com> (raw)
In-Reply-To: <y0miqyb435a.fsf@ton.toronto.redhat.com>
On Mon, Apr 21, 2008 at 5:51 PM, Frank Ch. Eigler <fche@redhat.com> wrote:
> "Kai Henningsen" <kai.extern@googlemail.com> writes:
>
> > Maybe the largest problem (after the rather sparse documentation) is
> > that the pmacro system seems to be much weaker than GCC's iterator
> > system. [...] Right now, the best way I can think of is to generate
> > CGEN input with a Perl script ... [...]
>
> I agree, that is probably best.
>
>
> > 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. [...]
>
> Only you can judge that. There is little cgen-oriented development
> going on now, so any new features you need will need more
> encouragement & assistance to make happen than a Marvinoid moan.
So don't moan then.
Or in other words, rereading my mail I can't see anything even
remotely resembling a moan. What it mainly is is wondering what I
might have missed - it's hard to believe these particular problems
weren't apparent pretty much from the start, and thus it's hard to
believe nobody tried to solve them a long time ago.
And I'd like to hear how other people solved these kinds of problems -
or if they did.
next prev parent reply other threads:[~2008-04-21 19:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 8:12 Kai Henningsen
2008-04-21 19:06 ` Frank Ch. Eigler
2008-04-21 19:36 ` Kai Henningsen [this message]
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=7af24c80804211206x6e0f505fo1748b3af85a6d397@mail.gmail.com \
--to=kai.extern@googlemail.com \
--cc=cgen@sources.redhat.com \
--cc=fche@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).