qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Chen Qun <kuhn.chenqun@huawei.com>,
	qemu-devel@nongnu.org, qemu-trivial@nongnu.org
Cc: Euler Robot <euler.robot@huawei.com>,
	Laurent Vivier <laurent@vivier.eu>,
	ganqixin@huawei.com, zhang.zhanghailiang@huawei.com
Subject: Re: [PATCH 4/9] linux-user/mips/cpu_loop: silence the compiler warnings
Date: Wed, 28 Oct 2020 14:22:26 +0100	[thread overview]
Message-ID: <15244401-6423-aad2-c44d-30a1de4eeddd@redhat.com> (raw)
In-Reply-To: <20201028041819.2169003-5-kuhn.chenqun@huawei.com>

On 28/10/2020 05.18, Chen Qun wrote:
> When using -Wimplicit-fallthrough in our CFLAGS, the compiler showed warning:
> linux-user/mips/cpu_loop.c: In function ‘cpu_loop’:
> linux-user/mips/cpu_loop.c:104:24: warning: this statement may fall through [-Wimplicit-fallthrough=]
>   104 |                     if ((ret = get_user_ual(arg8, sp_reg + 28)) != 0) {
>       |                        ^
> linux-user/mips/cpu_loop.c:107:17: note: here
>   107 |                 case 7:
>       |                 ^~~~
> linux-user/mips/cpu_loop.c:108:24: warning: this statement may fall through [-Wimplicit-fallthrough=]
>   108 |                     if ((ret = get_user_ual(arg7, sp_reg + 24)) != 0) {
>       |                        ^
> linux-user/mips/cpu_loop.c:111:17: note: here
>   111 |                 case 6:
>       |                 ^~~~
> linux-user/mips/cpu_loop.c:112:24: warning: this statement may fall through [-Wimplicit-fallthrough=]
>   112 |                     if ((ret = get_user_ual(arg6, sp_reg + 20)) != 0) {
>       |                        ^
> linux-user/mips/cpu_loop.c:115:17: note: here
>   115 |                 case 5:
>       |                 ^~~~
> 
> Add the corresponding "fall through" comment to fix it.
> 
> Reported-by: Euler Robot <euler.robot@huawei.com>
> Signed-off-by: Chen Qun <kuhn.chenqun@huawei.com>
> ---
> Cc: Laurent Vivier <laurent@vivier.eu>
> ---
>  linux-user/mips/cpu_loop.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/linux-user/mips/cpu_loop.c b/linux-user/mips/cpu_loop.c
> index 553e8ca7f5..cfe7ba5c47 100644
> --- a/linux-user/mips/cpu_loop.c
> +++ b/linux-user/mips/cpu_loop.c
> @@ -104,18 +104,22 @@ void cpu_loop(CPUMIPSState *env)
>                      if ((ret = get_user_ual(arg8, sp_reg + 28)) != 0) {
>                          goto done_syscall;
>                      }
> +                    /* fall through */
>                  case 7:
>                      if ((ret = get_user_ual(arg7, sp_reg + 24)) != 0) {
>                          goto done_syscall;
>                      }
> +                    /* fall through */
>                  case 6:
>                      if ((ret = get_user_ual(arg6, sp_reg + 20)) != 0) {
>                          goto done_syscall;
>                      }
> +                    /* fall through */
>                  case 5:
>                      if ((ret = get_user_ual(arg5, sp_reg + 16)) != 0) {
>                          goto done_syscall;
>                      }
> +                    /* fall through */
>                  default:
>                      break;
>                  }

Reviewed-by: Thomas Huth <thuth@redhat.com>




  reply	other threads:[~2020-10-28 13:25 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-28  4:18 [PATCH 0/9] silence the compiler warnings Chen Qun
2020-10-28  4:18 ` [PATCH 1/9] target/i386: silence the compiler warnings in gen_shiftd_rm_T1 Chen Qun
2020-10-28 12:57   ` Thomas Huth
2020-10-28 13:20     ` Philippe Mathieu-Daudé
2020-10-28 15:31     ` Richard Henderson
2020-10-28 16:51       ` Thomas Huth
2020-10-29  2:40         ` Chenqun (kuhn)
2020-10-28 15:31   ` Richard Henderson
2020-10-28  4:18 ` [PATCH 2/9] hw/intc/arm_gicv3_kvm: silence the compiler warnings Chen Qun
2020-10-28 20:20   ` Peter Maydell
2020-10-28  4:18 ` [PATCH 3/9] accel/tcg/user-exec: " Chen Qun
2020-10-28 13:52   ` Thomas Huth
2020-10-28 15:37     ` Richard Henderson
2020-10-29  6:13       ` Chenqun (kuhn)
2020-10-28  4:18 ` [PATCH 4/9] linux-user/mips/cpu_loop: " Chen Qun
2020-10-28 13:22   ` Thomas Huth [this message]
2020-10-28  4:18 ` [PATCH 5/9] target/sparc/translate: " Chen Qun
2020-10-28  6:39   ` Artyom Tarasenko
2020-10-28  9:50   ` Philippe Mathieu-Daudé
2020-10-28  4:18 ` [PATCH 6/9] target/sparc/win_helper: " Chen Qun
2020-10-28  6:42   ` Artyom Tarasenko
2020-10-28  9:51   ` Philippe Mathieu-Daudé
2020-10-29  2:45     ` Chenqun (kuhn)
2020-10-28  4:18 ` [PATCH 7/9] ppc: " Chen Qun
2020-10-28  4:29   ` David Gibson
2020-10-28 14:42     ` Thomas Huth
2020-10-28 23:38       ` David Gibson
2020-10-29  7:06         ` Chenqun (kuhn)
2020-10-28  4:18 ` [PATCH 8/9] target/ppc: " Chen Qun
2020-10-28  4:30   ` David Gibson
2020-10-28  9:56   ` Philippe Mathieu-Daudé
2020-10-28 15:06     ` Thomas Huth
2020-10-28 23:39       ` David Gibson
2020-10-29  7:16         ` Chenqun (kuhn)
2020-10-28  4:18 ` [PATCH 9/9] hw/timer/renesas_tmr: " Chen Qun
2020-10-28  9:59   ` Philippe Mathieu-Daudé
2020-10-28 15:04     ` Thomas Huth
2020-10-28 20:14       ` Peter Maydell
2020-10-29  8:26         ` Chenqun (kuhn)
2020-10-29  8:12     ` Chenqun (kuhn)

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=15244401-6423-aad2-c44d-30a1de4eeddd@redhat.com \
    --to=thuth@redhat.com \
    --cc=euler.robot@huawei.com \
    --cc=ganqixin@huawei.com \
    --cc=kuhn.chenqun@huawei.com \
    --cc=laurent@vivier.eu \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=zhang.zhanghailiang@huawei.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).