Related articles |
---|
C compiler front end wanted dg@cowlark.com (David Given) (2008-06-15) |
Re: C compiler front end wanted rich@pennware.com (Richard Pennington) (2008-06-15) |
Re: C compiler front end wanted dg@cowlark.com (David Given) (2008-06-15) |
Re: C compiler front end wanted sammyderoy@sympatico.ca (Sammy) (2008-06-15) |
Re: C compiler front end wanted torbenm@pc-003.diku.dk (2008-06-16) |
Re: C compiler front end wanted DrDiettrich1@aol.com (Hans-Peter Diettrich) (2008-06-15) |
Re: C compiler front end wanted monnier@iro.umontreal.ca (Stefan Monnier) (2008-06-17) |
Re: C compiler front end wanted dg@cowlark.com (David Given) (2008-06-20) |
Re: C compiler front end wanted mm.beck@gmx.net (Michael Beck) (2008-06-20) |
Re: C compiler front end wanted theresistor@gmail.com (2008-06-20) |
Re: C compiler front end wanted eliben@gmail.com (eliben) (2008-07-04) |
From: | David Given <dg@cowlark.com> |
Newsgroups: | comp.compilers |
Date: | Fri, 20 Jun 2008 00:55:45 +0100 |
Organization: | Disorganised |
References: | 08-06-027 |
Keywords: | C, tools |
Posted-Date: | 21 Jun 2008 12:57:37 EDT |
David Given wrote:
[...]
> Does anyone know if there are any clean, standalone libraries for
> parsing, verifying and then generating full ASTs, from C source code?
Thanks for all the replies; currently, sparse seems to be looking good
--- it even decomposes the expression trees into pseudo-code using
virtual registers in SSA form with liveness tracking, which means that
all I need to do is to bolt a noddy register allocator on the top and
I'm pretty much good to go. Very convenient.
However, it *is* all under construction and is totally undocumented,
which means I've got no idea if there are any gotchas coming up: but if
so, I've got plenty of other tools to look at. Thanks!
Return to the
comp.compilers page.
Search the
comp.compilers archives again.