From: Emese Revfy <re.emese@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Michal Marek <mmarek@suse.cz>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Kees Cook <keescook@chromium.org>
Subject: Re: linux-next: build warnings after merge of the kbuild tree
Date: Thu, 9 Jun 2016 19:42:25 +0200 [thread overview]
Message-ID: <20160609194225.be69ec2213a5cae71cba795b@gmail.com> (raw)
In-Reply-To: <20160609122258.1c2068f0@canb.auug.org.au>
On Thu, 9 Jun 2016 12:22:58 +1000
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Michal,
>
> After merging the kbuild tree, today's linux-next build (x86_64
> allmodconfig) produced these warnings:
>
> Cyclomatic Complexity 1 scripts/mod/devicetable-offsets.c:main
> Cyclomatic Complexity 1 kernel/bounds.c:foo
> Cyclomatic Complexity 1 arch/x86/kernel/asm-offsets_64.c:main
> Cyclomatic Complexity 1 arch/x86/kernel/asm-offsets.c:common
> Cyclomatic Complexity 5 arch/x86/ia32/audit.c:ia32_classify_syscall
>
> and so on (many, many of these - about 635,000 :-()
>
> Introduced (presumably) by commits
>
> 6b90bd4ba40b ("GCC plugin infrastructure")
> 0dae776c6bf3 ("Add Cyclomatic complexity GCC plugin")
>
> I have disabled CONFIG_GCC_PLUGIN_CYC_COMPLEXITY (by making it depend
> on CONFIG_BROKEN) until it is not enabled by default.
These aren't warnings. This plugin is a static analyzer. It prints out
the cyclomatic complexity of all functions in the kernel.
I think it would be useful to enable it sometimes and report new functions
with a high enough complexity value.
--
Emese
next prev parent reply other threads:[~2016-06-09 17:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 2:22 linux-next: build warnings after merge of the kbuild tree Stephen Rothwell
2016-06-09 2:56 ` Kees Cook
2016-06-09 4:05 ` Stephen Rothwell
2016-06-09 10:57 ` Michal Marek
2016-06-09 17:37 ` Emese Revfy
2016-06-09 17:58 ` Kees Cook
2016-06-09 11:10 ` Michael Ellerman
2016-06-09 17:42 ` Emese Revfy [this message]
2016-08-17 1:44 Stephen Rothwell
2016-08-17 12:59 ` Michal Marek
2016-08-18 1:09 ` Nicholas Piggin
2016-08-19 3:38 ` Stephen Rothwell
2016-08-19 5:09 ` Stephen Rothwell
2016-08-19 5:32 ` Nicholas Piggin
2016-08-19 8:37 ` Michal Marek
2016-08-19 10:44 ` Nicholas Piggin
2016-08-22 10:47 ` Nicholas Piggin
2016-08-26 3:58 ` Nicholas Piggin
2016-08-26 6:21 ` Nicholas Mc Guire
2017-07-19 0:05 Stephen Rothwell
2018-05-30 22:40 Stephen Rothwell
2018-05-31 1:12 ` Masahiro Yamada
2018-05-31 1:26 ` Kees Cook
2018-05-31 3:53 ` Kees Cook
2018-06-01 1:56 ` Masahiro Yamada
2018-06-01 4:01 ` Kees Cook
2018-06-02 20:39 ` Arnd Bergmann
2018-06-04 8:39 ` Arnd Bergmann
2019-09-04 0:13 Stephen Rothwell
2019-09-04 1:00 ` Masahiro Yamada
2019-09-04 6:22 ` Masahiro Yamada
2019-09-04 12:33 ` Stephen Rothwell
2019-09-04 12:32 ` Stephen Rothwell
2022-06-01 23:28 Stephen Rothwell
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=20160609194225.be69ec2213a5cae71cba795b@gmail.com \
--to=re.emese@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sfr@canb.auug.org.au \
/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).