On Sat, Nov 10, 2007 at 09:37:51AM +0000, J.H.M. Dassen (Ray) wrote: > Package: sparse > Version: 0.4-2 > Severity: normal > > On amd64, both "unsigned long" and "unsigned long long" are 64 bits. On this > architecture, I would therefore expect sparse to generate the same warnings > relating to both types. This is not the case however, as illustrated by the > test code below. Is this a bug in sparse, or am I misunderstanding sparse's > behaviour in this case?
No you're not, for some reason when building on a biarch machine you have to tell him you want the 64bits API. Run: cgcc -m64 .... yourtest.c and it will work as expected. cgcc is a tiny wrapper, and I believe it's the place where you have to fix that -m64 for sparse. I'll have a deeper look. -- ·O· Pierre Habouzit ··O [EMAIL PROTECTED] OOO http://www.madism.org
pgpw8kIpxRnnG.pgp
Description: PGP signature
