linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Christopher Li <sparse@chrisli.org>
Cc: nkavv@physics.auth.gr, linux-sparse@vger.kernel.org
Subject: Re: Backend projects for Sparse
Date: Wed, 28 Nov 2007 14:45:13 -0500	[thread overview]
Message-ID: <474DC549.2030000@garzik.org> (raw)
In-Reply-To: <70318cbf0711281053k6dc561c5ge540ccd99a6a922e@mail.gmail.com>

Christopher Li wrote:
> There is already compile-i386.c in the project. But it is not a good
> place to start.

Agreed.  That was generating code directly from the parse tree, rather 
than from the linearized form.


> 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.


>> 5) Is there any documentation covering the API and linked tools to the sparse
>> library (something more than the man pages)?
> 
> Not that I know of. If you need that much detail to perform the back end work,
> you have to read some source code. I think you can ignore a lot of the parser
> details and focus on the linearized byte code.

Agreed.

	Jeff

  parent reply	other threads:[~2007-11-28 19:45 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 [this message]
2007-11-28 20:27     ` 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=474DC549.2030000@garzik.org \
    --to=jeff@garzik.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=nkavv@physics.auth.gr \
    --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).