From: Gerd Hoffmann <kraxel@redhat.com>
To: "Volker Rümelin" <vr_qemu@t-online.de>
Cc: "Alexander Bulekov" <alxndr@bu.edu>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
QEMU <qemu-devel@nongnu.org>
Subject: Re: [PATCH] audio/mixeng: fix clang 10+ warning
Date: Tue, 26 May 2020 07:51:10 +0200 [thread overview]
Message-ID: <20200526055110.xhqlolr4l6on2wya@sirius.home.kraxel.org> (raw)
In-Reply-To: <20200523201712.23908-1-vr_qemu@t-online.de>
On Sat, May 23, 2020 at 10:17:12PM +0200, Volker Rümelin wrote:
> The code in CONV_NATURAL_FLOAT() and CLIP_NATURAL_FLOAT()
> seems to use the constant 2^31-0.5 to convert float to integer
> and back. But the float type lacks the required precision and
> the constant used for the conversion is 2^31. This is equiva-
> lent to a [-1.f, 1.f] <-> [INT32_MIN, INT32_MAX + 1] mapping.
>
> This patch explicitly writes down the used constant. The
> compiler generated code doesn't change.
>
> The constant 2^31 has an exact float representation and the
> clang 10 compiler stops complaining about an implicit int to
> float conversion with a changed value.
>
> A few notes:
> - The conversion of 1.f to INT32_MAX + 1 doesn't overflow. The
> type of the destination variable is int64_t.
> - At a later stage one of the clip_* functions in
> audio/mixeng_template.h limits INT32_MAX + 1 to the integer
> range.
> - The clip_natural_float_* functions in audio/mixeng.c convert
> INT32_MAX and INT32_MAX + 1 to 1.f.
>
> Buglink: https://bugs.launchpad.net/bugs/1878627
> Signed-off-by: Volker Rümelin <vr_qemu@t-online.de>
Added to audio queue.
thanks,
Gerd
prev parent reply other threads:[~2020-05-26 5:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-23 20:16 [PATCH 0/1] audio/mixeng: fix clang 10+ warning Volker Rümelin
2020-05-23 20:17 ` [PATCH] " Volker Rümelin
2020-05-26 5:51 ` Gerd Hoffmann [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=20200526055110.xhqlolr4l6on2wya@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=alxndr@bu.edu \
--cc=f4bug@amsat.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=vr_qemu@t-online.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.