From: Laszlo Ersek <lersek@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Eduardo Habkost <ehabkost@redhat.com>,
qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>,
Paolo Bonzini <pbonzini@redhat.com>,
Joseph Myers <joseph@codesourcery.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH] target/i386: floatx80: avoid compound literals in static initializers
Date: Fri, 17 Jul 2020 11:27:31 +0200 [thread overview]
Message-ID: <d49ed94c-8095-2803-9fef-e7d0396f2ed6@redhat.com> (raw)
In-Reply-To: <87y2njv2to.fsf@linaro.org>
On 07/16/20 18:31, Alex Bennée wrote:
>
> Laszlo Ersek <lersek@redhat.com> writes:
>
>> Quoting ISO C99 6.7.8p4, "All the expressions in an initializer for an
>> object that has static storage duration shall be constant expressions or
>> string literals".
>>
>> The compound literal produced by the make_floatx80() macro is not such a
>> constant expression, per 6.6p7-9. (An implementation may accept it,
>> according to 6.6p10, but is not required to.)
>>
>> Therefore using "floatx80_zero" and make_floatx80() for initializing
>> "f2xm1_table" and "fpatan_table" is not portable. And gcc-4.8 in RHEL-7.6
>> actually chokes on them:
>>
>>> target/i386/fpu_helper.c:871:5: error: initializer element is not constant
>>> { make_floatx80(0xbfff, 0x8000000000000000ULL),
>>> ^
>>
>> We've had the make_floatx80_init() macro for this purpose since commit
>> 3bf7e40ab914 ("softfloat: fix for C99", 2012-03-17), so let's use that
>> macro again.
>>
>> Fixes: eca30647fc07
>> Fixes: ff57bb7b6326
>> Link: https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg06566.html
>> Link: https://lists.gnu.org/archive/html/qemu-devel/2020-07/msg04714.html
>> Cc: Alex Bennée <alex.bennee@linaro.org>
>> Cc: Aurelien Jarno <aurelien@aurel32.net>
>> Cc: Eduardo Habkost <ehabkost@redhat.com>
>> Cc: Joseph Myers <joseph@codesourcery.com>
>> Cc: Paolo Bonzini <pbonzini@redhat.com>
>> Cc: Peter Maydell <peter.maydell@linaro.org>
>> Cc: Richard Henderson <rth@twiddle.net>
>> Signed-off-by: Laszlo Ersek <lersek@redhat.com>
>> ---
>>
>> Notes:
>> I can see that there are test cases under "tests/tcg/i386", but I don't
>> know how to run them.
>
> You can run the TCG tests with:
>
> make check-tcg
>
> or more specifically:
>
> make run-tcg-tests-i386-linux-user
>
> there is also a:
>
> make check-softfloat
>
> although in this case nothing is affected.
>
> softfloat bits:
>
> Acked-by: Alex Bennée <alex.bennee@linaro.org>
Thank you!
Laszlo
prev parent reply other threads:[~2020-07-17 9:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 14:42 [PATCH] target/i386: floatx80: avoid compound literals in static initializers Laszlo Ersek
2020-07-16 15:09 ` Philippe Mathieu-Daudé
2020-07-17 9:26 ` Laszlo Ersek
2020-07-17 16:46 ` Laszlo Ersek
2020-07-17 18:19 ` Philippe Mathieu-Daudé
2020-07-21 16:02 ` Alex Bennée
2020-07-22 17:52 ` Laszlo Ersek
2020-07-16 16:31 ` Alex Bennée
2020-07-17 9:27 ` Laszlo Ersek [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=d49ed94c-8095-2803-9fef-e7d0396f2ed6@redhat.com \
--to=lersek@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=aurelien@aurel32.net \
--cc=ehabkost@redhat.com \
--cc=joseph@codesourcery.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).