linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Lattner <sabre@nondot.org>
To: linux-sparse@vger.kernel.org
Subject: New LLVM C front-end
Date: Fri, 13 Jul 2007 09:54:25 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.62.0707130940060.26974@nondot.org> (raw)


Hi Sparsers,

We've recently been building a new C front-end for LLVM from scratch. 
Information about it is here:
http://lists.cs.uiuc.edu/pipermail/llvmdev/2007-July/009817.html

The work is still somewhat early (for example, though the parser is quite 
far along, we don't emit all warnings and errors that we should, and the 
code generator doesn't support many constructs yet), but we're pursuing it 
aggressively.  Over the next couple years, we hope to grow it out to 
include full C++ support as well as C.

Compared to sparse, some goals are similiar: provide an extremely fast C 
parser (including preprocessor, type checker, etc) which can be reused by 
many different clients (static analysis, refactoring, indexing, etc).

Others goal are different.  In contrast to sparse, we aim (in the short 
term) to provide strict ISO standards compliance, support for a full suite 
of GCC extensions (whether they are well considered or not :-/ ), and code 
generation support through LLVM.  Also, the code is BSD licensed.

This email is only intended as an FYI, so I'll keep it short.  If you have 
any questions, please ask on the cfe-dev list:
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev

-Chris

-- 
http://nondot.org/sabre/
http://llvm.org/

                 reply	other threads:[~2007-07-13 16:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=Pine.LNX.4.62.0707130940060.26974@nondot.org \
    --to=sabre@nondot.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).