From: Randy Dunlap <rdunlap@infradead.org>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Ramsay Jones <ramsay@ramsayjones.plus.com>,
Sparse Mailing-list <linux-sparse@vger.kernel.org>
Subject: Re: sparse v0.6.4
Date: Sat, 21 May 2022 08:51:02 -0700 [thread overview]
Message-ID: <7a38638d-8d91-b86c-b24c-8db21e46b83d@infradead.org> (raw)
In-Reply-To: <20220521135428.g5l47v2lsltv7lod@mail>
On 5/21/22 06:54, Luc Van Oostenryck wrote:
> On Fri, Jan 14, 2022 at 08:25:31PM -0800, Randy Dunlap wrote:
>> Hi Luc,
>
> Hi Randy,
>
> Apologies for this reply delayed for much too long.
Hey Luc,
>
>> 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.)
>
> Yes indeed, it was one of the things added in this release.
>
>> .. 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?
>
> Do you still see these? If yes, can you tell a bit about your setup and
> the exact command line used?
No, I no longer see these warnings. :)
> I'm asking because I never saw a problem with this, same for the test bots.
> It should be exactly the same as for any other predefined value.
> However, as predefined, they should all be reported from 'builtin:0:0:'
> and the 'builtin:1:9:' look as if those are from a '-include <somefile.h>'
> on the command line.
>
> Best regards,
> -- Luc
Thanks.
--
~Randy
next prev parent reply other threads:[~2022-05-21 15:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 18:53 sparse v0.6.4 Ramsay Jones
2021-09-07 6:14 ` Luc Van Oostenryck
2022-01-15 4:25 ` Randy Dunlap
2022-05-21 13:54 ` Luc Van Oostenryck
2022-05-21 15:51 ` Randy Dunlap [this message]
2022-06-14 0:17 ` [PATCH] predefine __ATOMIC_ACQUIRE & friends as weak Luc Van Oostenryck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7a38638d-8d91-b86c-b24c-8db21e46b83d@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--cc=ramsay@ramsayjones.plus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).