From: Kamil Dudka <kdudka@redhat.com>
To: Christopher Li <sparse@chrisli.org>
Cc: Jeff Garzik <jeff@garzik.org>,
Sparse Mailing-list <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH] compile-i386: do not generate an infinite loop
Date: Wed, 22 Jul 2009 11:24:35 +0200 [thread overview]
Message-ID: <200907221124.35339.kdudka@redhat.com> (raw)
In-Reply-To: <70318cbf0907220138g412388fam12f31f03c25ebf1f@mail.gmail.com>
On Wed July 22 2009 10:38:43 Christopher Li wrote:
> Adding Jeff to the CC list. The compile-i386.c is Jeff's pet project.
> The change looks good to me. I would like to give Jeff some time
> to comment it before I apply the patch.
Thanks!
> BTW, have you take a look at Linus's example.c? It is based on the
> linearized byte code and It does more advance stuff like simple
> register allocation. In my opinion example.c is a better place to start
> hacking compiler back end than compile.c
Linus's example.c works fine with the same test-case. I decided to take
compile.c as template just because it doesn't use the linearized code.
The tree structure better accomplishes my requirements for now. Maybe I'll
turn to byte code in future. I've just started to play with it.
Anyway SPARSE seems to be quite helpful. It's easy to read and can save
a lot of development time while processing C sources.
Kamil
next prev parent reply other threads:[~2009-07-22 9:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 21:34 [PATCH] compile-i386: do not generate an infinite loop Kamil Dudka
2009-07-22 8:38 ` Christopher Li
2009-07-22 9:24 ` Kamil Dudka [this message]
2009-07-22 16:34 ` Christopher Li
2009-07-22 17:21 ` Kamil Dudka
2009-07-22 19:30 ` Christopher Li
2009-07-22 12:45 ` Jeff Garzik
2009-07-22 16:39 ` Christopher Li
2009-07-22 16:51 ` Jeff Garzik
2009-07-22 17:02 ` Kamil Dudka
2009-07-22 19:18 ` Christopher Li
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=200907221124.35339.kdudka@redhat.com \
--to=kdudka@redhat.com \
--cc=jeff@garzik.org \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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 NNTP newsgroup(s).