On Mon, Aug 29, 2011 at 05:42:49PM +0300, 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? Take a look at the cgcc script. Most of what it does to handle target-specific information should occur in sparse instead. - Josh Triplett -- 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
