From: Oleg Nesterov <oleg@redhat.com>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Alexey Gladkov <gladkov.alexey@gmail.com>, linux-sparse@vger.kernel.org
Subject: Re: [PATCH] Add symantic index utility
Date: Tue, 10 Mar 2020 16:07:14 +0100 [thread overview]
Message-ID: <20200310150713.GB19012@redhat.com> (raw)
In-Reply-To: <20200309223701.dbnej7esb4qp56bm@ltop.local>
On 03/09, Luc Van Oostenryck wrote:
>
> On Mon, Mar 09, 2020 at 04:25:09PM +0100, Alexey Gladkov wrote:
> > sindex is the simple to use cscope-like tool based on sparse/dissect.
> > Unlike cscope it runs after pre-processor and thus it can't index the
> > code filtered out by ifdef's, but otoh it understands how the symbol
> > is used and it can track the usage of struct members.
>
> Hi,
>
> This looks pretty good.
> I just have a few non-essential remarks I've added here below.
Great, thanks!
while Alexey is working on your comments...
> > To create an index for your linux kernel configuration:
> >
> > $ make C=2 CHECK="sindex add --"
Annoyingly, this triggers a lot of sparse_error's in pre-process.c:collect_arg().
And just in case, of course this is not specific to dissect/sindex, ./sparse or
anything else will equally complain.
For example,
1011 static inline bool page_expected_state(struct page *page,
1012 unsigned long check_flags)
1013 {
1014 if (unlikely(atomic_read(&page->_mapcount) != -1))
1015 return false;
1016
1017 if (unlikely((unsigned long)page->mapping |
1018 page_ref_count(page) |
1019 #ifdef CONFIG_MEMCG
1020 (unsigned long)page->mem_cgroup |
1021 #endif
1022 (page->flags & check_flags)))
1023 return false;
1024
1025 return true;
1026 }
leads to
mm/page_alloc.c:1019:1: error: directive in macro's argument list
mm/page_alloc.c:1021:1: error: directive in macro's argument list
and it is not immediately clear why. Yes, because "unlikely" is a macro.
Can't we simply remove this sparse_error() ? "#if" inside the macro's args
is widely used in kernel, gcc doesn't complain, afaics pre-process.c handles
this case correctly.
With the patch below
$ make -s -j4 C=2 CHECK='sindex add --'
in my dev tree is really silent:
kernel/events/core.c:571:26: warning: function 'perf_pmu_name' with external linkage has definition
arch/x86/kernel/kprobes/opt.c:468:13: warning: function 'arch_unoptimize_kprobes' with external linkage has definition
and both warnings look valid.
Oleg.
--- a/pre-process.c
+++ b/pre-process.c
@@ -271,8 +271,6 @@ static struct token *collect_arg(struct token *prev, int vararg, struct position
while (!eof_token(next = scan_next(p))) {
if (next->pos.newline && match_op(next, '#')) {
if (!next->pos.noexpand) {
- sparse_error(next->pos,
- "directive in macro's argument list");
preprocessor_line(stream, p);
__free_token(next); /* Free the '#' token */
continue;
next prev parent reply other threads:[~2020-03-10 15:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 15:25 [PATCH] Add symantic index utility Alexey Gladkov
2020-03-09 22:37 ` Luc Van Oostenryck
2020-03-10 15:07 ` Oleg Nesterov [this message]
2020-03-10 17:12 ` Luc Van Oostenryck
2020-03-11 12:04 ` Oleg Nesterov
2020-03-11 16:47 ` Luc Van Oostenryck
2020-03-11 9:07 ` Dan Carpenter
2020-03-11 11:33 ` Oleg Nesterov
2020-03-11 17:11 ` Luc Van Oostenryck
2020-03-11 17:06 ` 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=20200310150713.GB19012@redhat.com \
--to=oleg@redhat.com \
--cc=gladkov.alexey@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.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