Posted Oct 18, 2006 7:20 UTC (Wed) by xoddam
In reply to: Not Enough
Parent article: FSF should separate GPLv3 changes (Linux.com)
The sparse C parser & checker. The FAQ begins:
Q. Why not just use gcc?
A. Gcc is big, complex, and the gcc maintainers are not interested in
other uses of the gcc front-end. In fact, gcc has explicitly
resisted splitting up the front and back ends and having some common
intermediate language because or religious license issues - you can
have multiple front ends and back ends, but they all have to be part
of gcc and licensed under the GPL.
This all (in my opinion) makes gcc development harder than it should
be, and makes the end result very ungainly. With "sparse", the
front-end is very explicitly separated into its own independent
project, and is totally independent from the users. I don't want to
know what you do in the back-end, because I don't think I _should_
know or care.
Q. Why not GPL?
A. See the previous question: I personally think that the front end
must be a totally separate project from the back end: any other
approach just leads to insanity. However, at the same time clearly
we cannot write intermediate files etc crud...
There isn't a web page for this software and no-one packages it
AFAICT, which is pretty unusual. It's developed more-or-less in sync
with the kernel and the 'sparse annotations' of the kernel source. You
have to fetch the git repository before you can read the FAQ...
(or a tarball from here)
to post comments)