linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Triplett <josh@freedesktop.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: Matt Domsch <Matt_Domsch@dell.com>, linux-sparse@vger.kernel.org
Subject: Re: sparse as a compiler front-end
Date: Sat, 11 Nov 2006 17:32:32 -0800	[thread overview]
Message-ID: <455679B0.8030106@freedesktop.org> (raw)
In-Reply-To: <45564680.8090806@garzik.org>

[-- Attachment #1: Type: text/plain, Size: 671 bytes --]

Jeff Garzik wrote:
> I see that sparse made it into Fedora Extras, so that 'yum install' 
> automatically pulls it down for me.  Yay!  Thanks, Matt.

Thanks indeed.

> Can libsparse.a and necessary includes be packaged as well?

Sure, assuming you don't mind coding against something potentially fluid.  The
next release will install the library and headers.  (At the moment, "necessary
headers" seems to mean "all of them".)

> I have wild ambitions of rewriting compile-i386.c (my int-only x86 
> pseudo-compiler) using the new basic block stuff, into a proper [if very 
> very basic] C99 compiler.

I look forward to seeing that.

- Josh Triplett


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  parent reply	other threads:[~2006-11-12  1:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-11 21:54 sparse as a compiler front-end Jeff Garzik
2006-11-11 23:50 ` Matt Domsch
2006-11-12  1:45   ` Jeff Garzik
2006-11-12  3:04     ` Matt Domsch
2006-11-12  3:22       ` Jeff Garzik
2006-11-12  1:32 ` Josh Triplett [this message]
2006-12-05 16:53   ` Josh Triplett
2006-12-08 19:34     ` Matt Domsch
2006-12-09  9:43       ` Josh Triplett
2006-12-09 10:15         ` Jeff Garzik
2007-02-28  1:36           ` Josh Triplett
2006-12-09 10:17       ` Jeff Garzik
2006-12-09 16:17         ` Matt Domsch

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=455679B0.8030106@freedesktop.org \
    --to=josh@freedesktop.org \
    --cc=Matt_Domsch@dell.com \
    --cc=jeff@garzik.org \
    --cc=linux-sparse@vger.kernel.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).