qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "wangyanan (Y)" via <qemu-devel@nongnu.org>
To: Thomas Huth <thuth@redhat.com>, <qemu-devel@nongnu.org>,
	Alistair Francis <alistair.francis@wdc.com>
Cc: Andrew Jones <drjones@redhat.com>,
	David Gibson <david@gibson.dropbear.id.au>,
	<qemu-trivial@nongnu.org>
Subject: Re: [PATCH] softmmu/device_tree: Silence compiler warning with --enable-sanitizers
Date: Mon, 10 Jan 2022 10:03:54 +0800	[thread overview]
Message-ID: <f0fe5c41-dd9e-ffed-bac4-fa634f633af1@huawei.com> (raw)
In-Reply-To: <20220107133844.145039-1-thuth@redhat.com>


On 2022/1/7 21:38, Thomas Huth wrote:
> If I configure my build with --enable-sanitizers, my GCC (v8.5.0)
> complains:
>
> .../softmmu/device_tree.c: In function ‘qemu_fdt_add_path’:
> .../softmmu/device_tree.c:560:18: error: ‘retval’ may be used uninitialized
>   in this function [-Werror=maybe-uninitialized]
>       int namelen, retval;
>                    ^~~~~~
>
> It's a false warning since the while loop is always executed at least
> once (p has to be non-NULL, otherwise the derefence in the if-statement
> earlier will crash). Thus let's switch to a do-while loop here instead
> to make the compiler happy in all cases.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>   softmmu/device_tree.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: Yanan Wang <wangyanan55@huawei.com>
> diff --git a/softmmu/device_tree.c b/softmmu/device_tree.c
> index 3965c834ca..9e96f5ecd5 100644
> --- a/softmmu/device_tree.c
> +++ b/softmmu/device_tree.c
> @@ -564,7 +564,7 @@ int qemu_fdt_add_path(void *fdt, const char *path)
>           return -1;
>       }
>   
> -    while (p) {
> +    do {
>           name = p + 1;
>           p = strchr(name, '/');
>           namelen = p != NULL ? p - name : strlen(name);
> @@ -584,7 +584,7 @@ int qemu_fdt_add_path(void *fdt, const char *path)
>           }
>   
>           parent = retval;
> -    }
> +    } while (p);
>   
>       return retval;
>   }



  parent reply	other threads:[~2022-01-10  2:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07 13:38 [PATCH] softmmu/device_tree: Silence compiler warning with --enable-sanitizers Thomas Huth
2022-01-07 14:45 ` Andrew Jones
2022-01-07 14:47 ` Philippe Mathieu-Daudé
2022-01-07 20:18 ` Richard Henderson
2022-01-10  2:10   ` wangyanan (Y) via
2022-01-08  0:22 ` Alistair Francis
2022-01-10  2:03 ` wangyanan (Y) via [this message]
2022-01-10  6:39 ` Alistair Francis

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=f0fe5c41-dd9e-ffed-bac4-fa634f633af1@huawei.com \
    --to=qemu-devel@nongnu.org \
    --cc=alistair.francis@wdc.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=drjones@redhat.com \
    --cc=qemu-trivial@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=wangyanan55@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).