From: "Christopher Li" <sparse@chrisli.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: nkavv@physics.auth.gr, linux-sparse@vger.kernel.org
Subject: Re: Backend projects for Sparse
Date: Wed, 28 Nov 2007 12:27:46 -0800 [thread overview]
Message-ID: <70318cbf0711281227n4f41fe88hef0ac9432102a563@mail.gmail.com> (raw)
In-Reply-To: <474DC549.2030000@garzik.org>
On Nov 28, 2007 11:45 AM, Jeff Garzik <jeff@garzik.org> wrote:
> Christopher Li wrote:
> > It does not use the linearized byte code at all. The compile.c written by Linus
> > is a better place to start.
>
> test-linearize.c maybe? compile.c is part of compile-i386.
Ah, you are right. I mix it up. It should be the "example.c" instead.
test-linearize.c just print out the linearized byte codes.
Chris
prev parent reply other threads:[~2007-11-28 20:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 9:53 Backend projects for Sparse nkavv
2007-11-28 18:53 ` Christopher Li
2007-11-28 19:00 ` Nikolaos Kavvadias
2007-11-28 19:25 ` Christopher Li
2007-11-29 9:09 ` nkavv
2007-11-28 19:45 ` Jeff Garzik
2007-11-28 20:27 ` Christopher Li [this message]
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=70318cbf0711281227n4f41fe88hef0ac9432102a563@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=jeff@garzik.org \
--cc=linux-sparse@vger.kernel.org \
--cc=nkavv@physics.auth.gr \
/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).