On Wed, Apr 29, 2009 at 3:43 PM, David Given <dg@xxxxxxxxxxx> wrote: > > In addition, I found a number of places where minor tweaks to what data > Sparse keeps around can make a compiler writer's life much easier; for > example, keeping more type data makes finding the type of a pseudo much > easier. There's a combined patch shipped with Clue that fixes and > enhances a bunch of this stuff: > > http://cluecc.svn.sourceforge.net/viewvc/cluecc/clue/sparse.patch?revision=34&view=markup I think some of your patch already went into sparse. If there are some missing. Feel free to submit it again. > (In fact, if you're generating llvm assembly directly, you may find it > easier just to add a backend to Clue rather than write your own, er, > middle-end --- a lot of the simplifications Clue does for languages like > Javascript also apply to llvm bitcode.) If every back end needs to do those "simplifications", that means sparse should be fixed to do it right. > <plug> Did I mention that Clue is now converting C into Java source that > runs at 40% of compiled C? </plug> Oh really, Java? Chris -- 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
