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
-
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
