From: Paul Burton <paul.burton@mips.com>
To: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
Cc: Robert Richter <rric@kernel.org>,
Ralf Baechle <ralf@linux-mips.org>,
Paul Burton <pburton@wavecomp.com>,
James Hogan <jhogan@kernel.org>,
"oprofile-list@lists.sf.net" <oprofile-list@lists.sf.net>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
Kees Cook <keescook@chromium.org>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>
Subject: Re: [PATCH] MIPS: OProfile: Mark expected switch fall-throughs
Date: Tue, 30 Jul 2019 16:44:28 +0000 [thread overview]
Message-ID: <MWHPR2201MB12774C1C54015019C8FD92EEC1DC0@MWHPR2201MB1277.namprd22.prod.outlook.com> (raw)
In-Reply-To: <20190729233209.GA28779@embeddedor>
Hello,
Gustavo A. R. Silva wrote:
> Mark switch cases where we are expecting to fall through.
>
> This patch fixes the following warning (Building: mips):
>
> arch/mips/oprofile/op_model_mipsxx.c: In function ‘mipsxx_cpu_stop’:
> arch/mips/oprofile/op_model_mipsxx.c:217:3: warning: this statement may fall through [-Wimplicit-fallthrough=]
> w_c0_perfctrl3(0);
> ^~~~~~~~~~~~~~~~~
> arch/mips/oprofile/op_model_mipsxx.c:218:2: note: here
> case 3:
> ^~~~
> arch/mips/oprofile/op_model_mipsxx.c:219:3: warning: this statement may fall through [-Wimplicit-fallthrough=]
> w_c0_perfctrl2(0);
> ^~~~~~~~~~~~~~~~~
> arch/mips/oprofile/op_model_mipsxx.c:220:2: note: here
> case 2:
> ^~~~
> arch/mips/oprofile/op_model_mipsxx.c:221:3: warning: this statement may fall through [-Wimplicit-fallthrough=]
> w_c0_perfctrl1(0);
> ^~~~~~~~~~~~~~~~~
> arch/mips/oprofile/op_model_mipsxx.c:222:2: note: here
> case 1:
> ^~~~
> arch/mips/oprofile/op_model_mipsxx.c: In function ‘mipsxx_cpu_start’:
> arch/mips/oprofile/op_model_mipsxx.c:197:3: warning: this statement may fall through [-Wimplicit-fallthrough=]
> w_c0_perfctrl3(WHAT | reg.control[3]);
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> arch/mips/oprofile/op_model_mipsxx.c:198:2: note: here
> case 3:
> ^~~~
> arch/mips/oprofile/op_model_mipsxx.c:199:3: warning: this statement may fall through [-Wimplicit-fallthrough=]
> w_c0_perfctrl2(WHAT | reg.control[2]);
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> arch/mips/oprofile/op_model_mipsxx.c:200:2: note: here
> case 2:
> ^~~~
> arch/mips/oprofile/op_model_mipsxx.c:201:3: warning: this statement may fall through [-Wimplicit-fallthrough=]
> w_c0_perfctrl1(WHAT | reg.control[1]);
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> arch/mips/oprofile/op_model_mipsxx.c:202:2: note: here
> case 1:
> ^~~~
> arch/mips/oprofile/op_model_mipsxx.c: In function ‘reset_counters’:
> arch/mips/oprofile/op_model_mipsxx.c:299:3: warning: this statement may fall through [-Wimplicit-fallthrough=]
> w_c0_perfcntr3(0);
> ^~~~~~~~~~~~~~~~~
> arch/mips/oprofile/op_model_mipsxx.c:300:2: note: here
> case 3:
> ^~~~
> arch/mips/oprofile/op_model_mipsxx.c:302:3: warning: this statement may fall through [-Wimplicit-fallthrough=]
> w_c0_perfcntr2(0);
> ^~~~~~~~~~~~~~~~~
> arch/mips/oprofile/op_model_mipsxx.c:303:2: note: here
> case 2:
> ^~~~
> arch/mips/oprofile/op_model_mipsxx.c:305:3: warning: this statement may fall through [-Wimplicit-fallthrough=]
> w_c0_perfcntr1(0);
> ^~~~~~~~~~~~~~~~~
> arch/mips/oprofile/op_model_mipsxx.c:306:2: note: here
> case 1:
> ^~~~
> arch/mips/oprofile/op_model_mipsxx.c: In function ‘mipsxx_perfcount_handler’:
> arch/mips/oprofile/op_model_mipsxx.c:242:6: warning: this statement may fall through [-Wimplicit-fallthrough=]
> if ((control & MIPS_PERFCTRL_IE) && ^
> arch/mips/oprofile/op_model_mipsxx.c:248:2: note: in expansion of macro ‘HANDLE_COUNTER’
> HANDLE_COUNTER(3)
> ^~~~~~~~~~~~~~
> arch/mips/oprofile/op_model_mipsxx.c:239:2: note: here
> case n + 1: ^
> arch/mips/oprofile/op_model_mipsxx.c:249:2: note: in expansion of macro ‘HANDLE_COUNTER’
> HANDLE_COUNTER(2)
> ^~~~~~~~~~~~~~
> arch/mips/oprofile/op_model_mipsxx.c:242:6: warning: this statement may fall through [-Wimplicit-fallthrough=]
> if ((control & MIPS_PERFCTRL_IE) && ^
> arch/mips/oprofile/op_model_mipsxx.c:249:2: note: in expansion of macro ‘HANDLE_COUNTER’
> HANDLE_COUNTER(2)
> ^~~~~~~~~~~~~~
> arch/mips/oprofile/op_model_mipsxx.c:239:2: note: here
> case n + 1: ^
> arch/mips/oprofile/op_model_mipsxx.c:250:2: note: in expansion of macro ‘HANDLE_COUNTER’
> HANDLE_COUNTER(1)
> ^~~~~~~~~~~~~~
> arch/mips/oprofile/op_model_mipsxx.c:242:6: warning: this statement may fall through [-Wimplicit-fallthrough=]
> if ((control & MIPS_PERFCTRL_IE) && ^
> arch/mips/oprofile/op_model_mipsxx.c:250:2: note: in expansion of macro ‘HANDLE_COUNTER’
> HANDLE_COUNTER(1)
> ^~~~~~~~~~~~~~
> arch/mips/oprofile/op_model_mipsxx.c:239:2: note: here
> case n + 1: ^
> arch/mips/oprofile/op_model_mipsxx.c:251:2: note: in expansion of macro ‘HANDLE_COUNTER’
> HANDLE_COUNTER(0)
> ^~~~~~~~~~~~~~
> CC usr/include/linux/pmu.h.s
> arch/mips/oprofile/op_model_mipsxx.c: In function ‘mipsxx_cpu_setup’:
> arch/mips/oprofile/op_model_mipsxx.c:174:3: warning: this statement may fall through [-Wimplicit-fallthrough=]
> w_c0_perfcntr3(reg.counter[3]);
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> arch/mips/oprofile/op_model_mipsxx.c:175:2: note: here
> case 3:
> ^~~~
> arch/mips/oprofile/op_model_mipsxx.c:177:3: warning: this statement may fall through [-Wimplicit-fallthrough=]
> w_c0_perfcntr2(reg.counter[2]);
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> arch/mips/oprofile/op_model_mipsxx.c:178:2: note: here
> case 2:
> ^~~~
> arch/mips/oprofile/op_model_mipsxx.c:180:3: warning: this statement may fall through [-Wimplicit-fallthrough=]
> w_c0_perfcntr1(reg.counter[1]);
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> arch/mips/oprofile/op_model_mipsxx.c:181:2: note: here
> case 1:
> ^~~~
>
> Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com>
Applied to mips-fixes.
Thanks,
Paul
[ This message was auto-generated; if you believe anything is incorrect
then please email paul.burton@mips.com to report it. ]
prev parent reply other threads:[~2019-07-30 16:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 23:32 [PATCH] MIPS: OProfile: Mark expected switch fall-throughs Gustavo A. R. Silva
2019-07-30 16:44 ` Paul Burton [this message]
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=MWHPR2201MB12774C1C54015019C8FD92EEC1DC0@MWHPR2201MB1277.namprd22.prod.outlook.com \
--to=paul.burton@mips.com \
--cc=gustavo@embeddedor.com \
--cc=jhogan@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=oprofile-list@lists.sf.net \
--cc=pburton@wavecomp.com \
--cc=ralf@linux-mips.org \
--cc=rric@kernel.org \
/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).