From: Thomas Huth <thuth@redhat.com>
To: marcandre.lureau@redhat.com, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
David Hildenbrand <david@redhat.com>,
Igor Mitsyanko <i.mitsyanko@gmail.com>,
Cornelia Huck <cohuck@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Beniamino Galvani <b.galvani@gmail.com>,
qemu-s390x@nongnu.org, qemu-arm@nongnu.org,
Antony Pavlov <antonynpavlov@gmail.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [PATCH 2/5] arm/digic: fix format-truncation warning
Date: Mon, 28 Mar 2022 11:21:38 +0200 [thread overview]
Message-ID: <9152b9c2-62a1-781e-ef99-f30cf633e050@redhat.com> (raw)
In-Reply-To: <20220328084717.367993-3-marcandre.lureau@redhat.com>
On 28/03/2022 10.47, marcandre.lureau@redhat.com wrote:
> From: Marc-André Lureau <marcandre.lureau@redhat.com>
>
> ../hw/arm/digic.c: In function ‘digic_init’:
> ../hw/arm/digic.c:45:54: error: ‘%d’ directive output may be truncated writing between 1 and 11 bytes into a region of size 5 [-Werror=format-truncation=]
> 45 | snprintf(name, DIGIC_TIMER_NAME_MLEN, "timer[%d]", i);
> | ^~
>
> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> ---
> hw/arm/digic.c | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/hw/arm/digic.c b/hw/arm/digic.c
> index 614232165cdc..6df554797734 100644
> --- a/hw/arm/digic.c
> +++ b/hw/arm/digic.c
> @@ -39,10 +39,7 @@ static void digic_init(Object *obj)
> object_initialize_child(obj, "cpu", &s->cpu, ARM_CPU_TYPE_NAME("arm946"));
>
> for (i = 0; i < DIGIC4_NB_TIMERS; i++) {
> -#define DIGIC_TIMER_NAME_MLEN 11
> - char name[DIGIC_TIMER_NAME_MLEN];
> -
> - snprintf(name, DIGIC_TIMER_NAME_MLEN, "timer[%d]", i);
> + g_autofree char *name = g_strdup_printf("timer[%d]", i);
> object_initialize_child(obj, name, &s->timer[i], TYPE_DIGIC_TIMER);
> }
>
DIGIC4_NB_TIMERS is 3 ... so the compiler should also be able to see that
the string fits fine into the name[] array here. That really sounds like
your GCC 12.0 is buggy. Please open a compiler bug ticket.
Thomas
next prev parent reply other threads:[~2022-03-28 9:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 8:47 [PATCH 0/5] Compilation fixes for 7.0 marcandre.lureau
2022-03-28 8:47 ` [PATCH 1/5] trace: fix compilation with lttng-ust >= 2.13 marcandre.lureau
2022-03-30 12:06 ` Stefan Hajnoczi
2022-03-31 15:45 ` Marc-André Lureau
2022-03-31 16:08 ` Stefan Hajnoczi
2022-03-28 8:47 ` [PATCH 2/5] arm/digic: fix format-truncation warning marcandre.lureau
2022-03-28 9:12 ` Peter Maydell
2022-03-28 9:21 ` Thomas Huth [this message]
2022-03-28 8:47 ` [PATCH 3/5] arm/allwinner-a10: fix format-overflow warning marcandre.lureau
2022-03-28 9:13 ` Peter Maydell
2022-03-28 8:47 ` [PATCH 4/5] intc/exynos4210_gic: " marcandre.lureau
2022-03-28 9:15 ` Peter Maydell
2022-03-29 17:07 ` Philippe Mathieu-Daudé
2022-03-29 17:23 ` Peter Maydell
2022-03-28 8:47 ` [PATCH 5/5] s390x/tcg: fix format-truncation warning marcandre.lureau
2022-03-28 8:58 ` Thomas Huth
2022-03-28 10:22 ` Marc-André Lureau
2022-03-28 10:57 ` Thomas Huth
2022-03-29 14:44 ` Thomas Huth
2022-03-28 9:01 ` David Hildenbrand
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=9152b9c2-62a1-781e-ef99-f30cf633e050@redhat.com \
--to=thuth@redhat.com \
--cc=antonynpavlov@gmail.com \
--cc=b.galvani@gmail.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=i.mitsyanko@gmail.com \
--cc=marcandre.lureau@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=stefanha@redhat.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).