Re: sparse v0.6.4

[Randy Dunlap <rdunlap@infradead.org>]

Hi Luc,

On 9/6/21 11:53, Ramsay Jones wrote:
> I have tested the new release, without issue, in the normal way on the
> usual platforms (32- & 64-bit Linux, 64-bit cygwin).
> 
> [Have you posted to the sparse mailing-list yet? I think my subscription
> has lapsed or something! I recently had to re-subscribe to the git
> mailing-list as well. :( ]

Odd, I didn't receive it either. No big deal, but I am just looking
at a kernel build issue when using sparse v0.6.4.

It seems that $subject version adds builtins for ATOMIC_ACQUIRE and
ATOMIC_RELEASE, but GCC has those too, so there are a few thousand
(OK, I didn't count them - I killed it quickly) of these: (e.g.)


..  CHECK   ../init/do_mounts_initrd.c
.command-line: note: in included file:
builtin:1:9: sparse: warning: preprocessor token __ATOMIC_ACQUIRE redefined
builtin:0:0: sparse: this was the original definition
builtin:1:9: sparse: warning: preprocessor token __ATOMIC_SEQ_CST redefined
builtin:0:0: sparse: this was the original definition
builtin:1:9: sparse: warning: preprocessor token __ATOMIC_ACQ_REL redefined
builtin:0:0: sparse: this was the original definition
builtin:1:9: sparse: warning: preprocessor token __ATOMIC_RELEASE redefined
builtin:0:0: sparse: this was the original definition

Any suggestions for how to avoid these warnings?

thanks.
-- 
~Randy