| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Josh Triplett <josh@freedesktop.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
The sparse interface is a kind of snaky that it change the input argument
array. The function sparse() does the same hack just to skip the files.
This patch add the ptr list for string. So sparse_initialize will
return list of file to compile. The string pointer is not aligned
at word boundary. This patch introduce non taged version of the ptr
list iteration function.
Signed-off-by: Christopher Li <sparse@chrisli.org>
|
|
|
|
|
|
| |
Noted by Mitesh Shah
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Start off with
sparse_initialize(argc, argv);
which will return the number of filenames found. You can then use that,
or just check if *argv is NULL in a loop like
while (*argv)
list = sparse(argv);
where you get the declaration list for each file in turn.
|
|
|
|
|
|
|
|
|
| |
It's disgusting how intimate lib.c is with all the types,
and this is slowly trying to split things up a bit. Now
the intimate part is in allocate.c, but maybe we can get
to the point where each allocation user just declares its
own allocation strategy, and just uses the generic routines
in allocate.c
|
|
|
|
| |
Make "obfuscate" use it too, and remove the old stale code.
|
| |
|
|
|
|
|
| |
Not only do all users want it, the list of used symbols
is not stable until after the tree has been evaluated.
|
|
|
|
|
| |
Use FOR_EACH_PTR() instead, or the much fancier iterators
for basic blocks.
|
|
|
|
| |
Pointed out by Mitesh shah <mshah@teja.com>
|
|
|
|
|
|
|
|
|
|
|
| |
warn->warning
error->error_die
new error
lib.h:
warn->warning
error->error_die
new error
Add gcc format checking to warning/error/...
|
|
|
|
| |
Maybe this makes us gcc-compatible. Maybe it doesn't.
|
|
|
|
| |
This makes "-m64" actually work.
|
|
|
|
| |
isn't the sole copyright owner these days.
|
| |
|
|
|
|
|
| |
type descriptions. Nothing interesting yet, though.
Oh, well.
|
|
Add "obfuscate" as a stupid back-end. It will generate some
really really horrible C output if I get my way.
Don't expose "attribute" for type attributes. Use only the
double-underscore version
|