Hi,
Consider the code:
unsigned int foo(unsigned long long x)
{
unsigned int tmp = x & 0x1fffffff;
return tmp;
}
sparse emits:
and.64 %r2 <- %arg1, $0x1fffffff
ret.32 %r2
%r2 seems to be interpreted as both 64 and 32 bits. Is this the
intended behavior? This could bring some trouble when we add
->ctype to pseudo..
- xi
--
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
