On 08/29/2011 10:42 AM, Pekka Enberg wrote:
On Sun, 28 Aug 2011, Jeff Garzik wrote:
* it will soon be necessary to pay more attention to target-specific
details. we need some mechanism for specifying i386, x86-64, etc. so
that we may fill in bits_in_pointer and similar values properly. This
may involve some sparse hacking IIRC, because sparse (used to be?)
largely hardcoded to use i386 target values when checking. Or maybe
this is already done, and I just am ignorant of that area of the code.
Can you think of anything else except target.c that needs to be fixed in
sparse?
struct layout is what immediately comes to mind. But it is mainly a
"only time will tell" answer, most likely.
Jeff
--
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
