[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] qtest: Fix bad printf format specifiers
From: |
Thomas Huth |
Subject: |
Re: [PATCH] qtest: Fix bad printf format specifiers |
Date: |
Sun, 8 Nov 2020 08:42:12 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 |
On 05/11/2020 09.19, Markus Armbruster wrote:
> Thomas Huth <thuth@redhat.com> writes:
>
>> On 04/11/2020 11.23, AlexChen wrote:
>>> We should use printf format specifier "%u" instead of "%d" for
>>> argument of type "unsigned int".
>>>
>>> Reported-by: Euler Robot <euler.robot@huawei.com>
>>> Signed-off-by: Alex Chen <alex.chen@huawei.com>
>>> ---
>>> tests/qtest/arm-cpu-features.c | 8 ++++----
>>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/tests/qtest/arm-cpu-features.c b/tests/qtest/arm-cpu-features.c
>>> index d20094d5a7..bc681a95d5 100644
>>> --- a/tests/qtest/arm-cpu-features.c
>>> +++ b/tests/qtest/arm-cpu-features.c
>>> @@ -536,7 +536,7 @@ static void test_query_cpu_model_expansion_kvm(const
>>> void *data)
>>> if (kvm_supports_sve) {
>>> g_assert(vls != 0);
>>> max_vq = 64 - __builtin_clzll(vls);
>>> - sprintf(max_name, "sve%d", max_vq * 128);
>>> + sprintf(max_name, "sve%u", max_vq * 128);
>>>
>>> /* Enabling a supported length is of course fine. */
>>> assert_sve_vls(qts, "host", vls, "{ %s: true }", max_name);
>>> @@ -556,7 +556,7 @@ static void test_query_cpu_model_expansion_kvm(const
>>> void *data)
>>> * unless all larger, supported vector lengths are also
>>> * disabled.
>>> */
>>> - sprintf(name, "sve%d", vq * 128);
>>> + sprintf(name, "sve%u", vq * 128);
>>> error = g_strdup_printf("cannot disable %s", name);
>>> assert_error(qts, "host", error,
>>> "{ %s: true, %s: false }",
>>> @@ -569,7 +569,7 @@ static void test_query_cpu_model_expansion_kvm(const
>>> void *data)
>>> * we need at least one vector length enabled.
>>> */
>>> vq = __builtin_ffsll(vls);
>>> - sprintf(name, "sve%d", vq * 128);
>>> + sprintf(name, "sve%u", vq * 128);
>>> error = g_strdup_printf("cannot disable %s", name);
>>> assert_error(qts, "host", error, "{ %s: false }", name);
>>> g_free(error);
>>> @@ -581,7 +581,7 @@ static void test_query_cpu_model_expansion_kvm(const
>>> void *data)
>>> }
>>> }
>>> if (vq <= SVE_MAX_VQ) {
>>> - sprintf(name, "sve%d", vq * 128);
>>> + sprintf(name, "sve%u", vq * 128);
>>> error = g_strdup_printf("cannot enable %s", name);
>>> assert_error(qts, "host", error, "{ %s: true }", name);
>>> g_free(error);
>>>
>>
>> max_vq and vq are both "uint32_t" and not "unsigned int" ... so if you want
>
> Not quite. They are, but the product isn't.
Ouch. Ok. Then let's go with this v1 patch instead of v2.
Thomas
- Re: [PATCH] qtest: Fix bad printf format specifiers, (continued)
- Re: [PATCH] qtest: Fix bad printf format specifiers, Markus Armbruster, 2020/11/06
- Re: [PATCH] qtest: Fix bad printf format specifiers, Philippe Mathieu-Daudé, 2020/11/06
- Re: [PATCH] qtest: Fix bad printf format specifiers, Markus Armbruster, 2020/11/06
- Re: [PATCH] qtest: Fix bad printf format specifiers, Thomas Huth, 2020/11/08
- Re: [PATCH] qtest: Fix bad printf format specifiers, Markus Armbruster, 2020/11/09
- Re: [PATCH] qtest: Fix bad printf format specifiers, Alex Chen, 2020/11/09
- Re: [PATCH] qtest: Fix bad printf format specifiers, Markus Armbruster, 2020/11/09
- Re: [PATCH] qtest: Fix bad printf format specifiers, Thomas Huth, 2020/11/10
- Re: [PATCH] qtest: Fix bad printf format specifiers, Markus Armbruster, 2020/11/11
Re: [PATCH] qtest: Fix bad printf format specifiers, Markus Armbruster, 2020/11/05
- Re: [PATCH] qtest: Fix bad printf format specifiers,
Thomas Huth <=