Re: dwarflint status

[Petr Machata <pmachata at redhat dot com>]

12.10.2010 20:43, Roland McGrath wrote:
> I assume the dwarflint/TODO file is up to date wrt everything you have
> done and yet have in mind to do.  Please let us know which things you
> expect to work on soon, if any.

TODO is up to date wrt what's done, meaning stuff that's done isn't 
there.  What's there is a couple of concrete checks that we'd like to 
have, and then a bunch of blue sky wishlist items.

> I have the impression that dwarflint today is pretty well feature-complete
> for the purpose of validating writer output as far as ensuring that it
> won't confuse libdw and dwarfcmp will be able to correctly compare an
> original and a rewritten file.  More kinds of checks and more polish are
> of course always good to have.  But the top concerns are just what we need
> to use it for self-tests/debugging of the compressor/writer work.  So I'd
> like to get an enumeration of any loose ends that might remain for those
> needs, to help us prioritize.

For debugging writer, dwarflint should be pretty much ready.  There are 
no significant loose ends, I think.  There's a lot of hackish code 
around that would benefit from generalizing, cleaning up, etc., but I 
could spend any amount of time on that.

Of course actual writer development will turn up a dozen weird edge 
cases that dwarflint mishandles.  Those will be instantly cannibalized 
as the test suite material.  There's about ten test cases right now, 
which is pathetic, given the crazy amount of branching that dwarflint does.

PM