From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-devel@nongnu.org,
"Daniel Henrique Barboza" <danielhb413@gmail.com>
Cc: qemu-ppc@nongnu.org, qemu-trivial@nongnu.org,
mrezanin@redhat.com, "Cédric Le Goater" <clg@kaod.org>,
"David Gibson" <david@gibson.dropbear.id.au>,
"Greg Kurz" <groug@kaod.org>
Subject: Re: [PATCH] libdecnumber/dpd/decimal64: Fix compiler warning from Clang 15
Date: Fri, 11 Nov 2022 08:43:35 +0100 [thread overview]
Message-ID: <37ed2651-936b-3ce3-2df4-f5a151e95971@redhat.com> (raw)
In-Reply-To: <eb8745ad-8075-c6ea-6fac-4437530c63b4@linaro.org>
On 10/11/2022 21.00, Philippe Mathieu-Daudé wrote:
> On 10/11/22 14:11, Thomas Huth wrote:
>> Clang 15 from Fedora 37 complains:
>>
>> ../libdecnumber/dpd/decimal64.c:620:8: error: variable 'n' set but
>> not used [-Werror,-Wunused-but-set-variable]
>> Int n; /* output bunch counter */
>> ^
>> 1 error generated.
>>
>> Remove the unused variable to silence the compiler warning.
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>> libdecnumber/dpd/decimal64.c | 3 +--
>> 1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> diff --git a/libdecnumber/dpd/decimal64.c b/libdecnumber/dpd/decimal64.c
>> index 4816176410..290dbe8177 100644
>> --- a/libdecnumber/dpd/decimal64.c
>> +++ b/libdecnumber/dpd/decimal64.c
>> @@ -617,7 +617,6 @@ static const uInt multies[]={131073, 26215, 5243,
>> 1049, 210};
>> #endif
>> void decDigitsToDPD(const decNumber *dn, uInt *targ, Int shift) {
>> Int cut; /* work */
>> - Int n; /* output bunch counter */
>> Int digits=dn->digits; /* digit countdown */
>> uInt dpd; /* densely packed decimal value */
>> uInt bin; /* binary value 0-999 */
>> @@ -676,7 +675,7 @@ void decDigitsToDPD(const decNumber *dn, uInt *targ,
>> Int shift) {
>> bin=0; /* [keep compiler quiet] */
>> #endif
>> - for(n=0; digits>0; n++) { /* each output bunch */
>> + while (digits > 0) { /* each output bunch */
>> #if DECDPUN==3 /* fast path, 3-at-a-time */
>> bin=*inu; /* 3 digits ready for convert */
>> digits-=3; /* [may go negative] */
>
> Or we could we backport the upstream fix :)
>
> https://gcc.gnu.org/git/?p=gcc.git;a=blobdiff;f=libdecnumber/dpd/decimal64.c;h=f72c5730ac3b473e2c334f604e7e52da9711fa72;hp=269eaecade5115a62e979897742cd5decec0681e;hb=8a79685989bff33f479d0ac2df0e18d55d3ba78b;hpb=e1d1842b5432472330384d1523bb3c3132c4fea0
I did not look on that code on purpose - it's licensed under the GPLv3, so
we should not mix that back into our GPLv2 version.
Thomas
next prev parent reply other threads:[~2022-11-11 8:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 13:11 [PATCH] libdecnumber/dpd/decimal64: Fix compiler warning from Clang 15 Thomas Huth
2022-11-10 13:41 ` Cédric Le Goater
2022-11-10 20:00 ` Philippe Mathieu-Daudé
2022-11-11 7:43 ` Thomas Huth [this message]
2022-11-11 10:09 ` Philippe Mathieu-Daudé
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=37ed2651-936b-3ce3-2df4-f5a151e95971@redhat.com \
--to=thuth@redhat.com \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=mrezanin@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=qemu-trivial@nongnu.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).