Messages in this thread | | | From | Kyle Moffett <> | Subject | Re: __STRICT_ANSI__ checks in headers | Date | Thu, 5 Oct 2006 04:56:39 -0400 |
| |
I'm away from my regular work systems at the moment, but I have a couple ideas:
On Oct 05, 2006, at 04:16:11, Ismail Donmez wrote: > 01 Eki 2006 Paz 12:14 tarihinde, Sam Ravnborg şunları yazmıştı: >> On Sun, Oct 01, 2006 at 10:34:56AM +0300, Ismail Donmez wrote: >>> On Sunday 01 October 2006 08:20, Kyle Moffett wrote: > [...] >>>> Just thinking about it we probably also need to educate sparse >>>> about >>>> __extension__ too. Perhaps somebody could also add an sparse >>>> flag to >>>> make it warn about nonportable constructs in exported header files. >>>> >>>> I'd submit a patch but my knowledge of kernel makefiles and >>>> depmod is >>>> somewhere between zero and none, exclusive. >>> >>> Thanks, I will have a look at it. >> >> I assume you will same errors from the in-kernel modpost. >> If you do not do so then there is some inconsistency between depmod >> and modpost that ougth to be fixed. > > The problem shows itself in the modpost, somehow __extension__ > clause seems to > foobar module CRC. I am not yet successfull on making modpost ignore > __extension__ .
Since GCC doesn't actually _do_ anything with __extension__ in the object output files, it must be a C-file-based parser problem, so you should probably be able to build one of the problematic modules and diff the resultant .cmd files, the .mod files, and the .mod.c files. Sorry I can't be of more help.
Cheers, Kyle Moffett- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |