Re: x86_64 compile spewing hundreds of warnings - started 2.6.15-git8

[Martin Bligh]

Martin Bligh wrote:
> between 2.6.15-git7 and 2.6.15-git8 we started getting hundreds of 
> compile warnings:
>
> -git7: http://test.kernel.org/20295/debug/test.log.0
> -git8: http://test.kernel.org/20402/debug/test.log.0
>
> Warnings look like this:
>
> include/asm/bitops.h: In function `load_elf32_binary':
> include/asm/bitops.h:30: warning: read-write constraint does not allow a 
> register
> include/asm/bitops.h:30: warning: read-write constraint does not allow a 
> register
> include/asm/bitops.h:65: warning: read-write constraint does not allow a 
> register
> include/asm/bitops.h:65: warning: read-write constraint does not allow a 
> register
> include/asm/bitops.h:30: warning: read-write constraint does not allow a 
> register
> include/asm/bitops.h:30: warning: read-write constraint does not allow a 
> register
> include/asm/bitops.h:65: warning: read-write constraint does not allow a 
> register
> include/asm/bitops.h:65: warning: read-write constraint does not allow a 
> register
> include/asm/bitops.h:30: warning: read-write constraint does not allow a 
> register
> include/asm/bitops.h:30: warning: read-write constraint does not allow a 
> register
> include/asm/bitops.h:65: warning: read-write constraint does not allow a 
> register
> include/asm/bitops.h:65: warning: read-write constraint does not allow a 
> register
>
>
> What do these mean? And how do we get rid of it?
>
> Presumably caused by this:
>
> http://www.kernel.org/git/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=636dd2b7def5c9c72551b51d4d516a65c269de08 
>
>
> or this:
>
> http://www.kernel.org/git/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=92934bcbf96bc9dc931c40ca5f1a57685b7b813b 

There were rumblings about changing these checks around a bit, but
nothing happened and the warnings are still there ... any chance of
fixing this?

M.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/