On Tue, Jan 29, 2019 at 12:57:09PM -0800, Jonathan Nieder wrote: > Hi Uwe, > > Uwe Kleine-König wrote: > > On 1/29/19 2:38 AM, Jonathan Nieder wrote: > > >> Thoughts of all kinds welcome, as always. If you'd prefer this in the > >> form of a "git pull"-able repository, a push to salsa, or an NMU, just > >> ask. > > > > I didn't follow sparse development in the nearer past. Is there a > > problem with sparse 0.5.2 that would be fixed by going to 0.6.0?
Yes, it does. Sparse 0.5.2 can't be used on recent glibc/gcc (like debian unstable), because their system headers use types _Float32, _Float64 & _Float128 which parse doesn't know about. This is fixed in v0.6.0. Sparse v0.6.0 contains also many others fixes and some improvements like, for example, Ramsay's patch. Another improvement is that its validation suite is substantially more complete (627 testfiles vs 288). > > My thought was not to touch it for buster and go to 0.6.0 only afterwards. > > Cc-ing Ramsay Jones and Luc to find out. In [1] I find > > | [I was a little surprised that Linux Mint 19.1 (based on Ubuntu > | 18.04) has v0.5.1 - Debian unstable has v0.5.2, but both of those > | are just a little too old for use with git on recent Linux.] > > but I wasn't able to reproduce a problem with v0.5.2 analyzing git.git > myself. It really depends on the distro you're using. > That said, v0.6.0 has been working well for me, so I suspect > upgrading is not too risky. It's my opinion too (but I admit that: * I'm sparse's maintainer and main developer * I mainly use & test sparse for kernel work, not userspace). -- Luc
