[PATCH 2/2] nptl: Convert tst-sem11 and tst-sem12 tests to use the test driver

Adhemerval Zanella Netto adhemerval.zanella@linaro.org
Mon Jul 15 17:34:34 GMT 2024



On 15/07/24 13:50, Maciej W. Rozycki wrote:
> On Mon, 15 Jul 2024, Maciej W. Rozycki wrote:
> 
>>>>>>> of which 90 failures in nptl/.  There may be issues with the compiler as 
>>>>>>> well (GCC 13.0.0 20221118).
>> [...]
>>>>  There have been 45 compilation failures like this:
>>>>
>>>> .../math/test-tgmath3-atan2.c: In function 'test_atan2_84':
>>>> .../math/test-tgmath3-atan2.c:903:59: error: conflicting types for 'var__Float32x'; have 'double'
>>>>   903 |   extern typeof (atan2 (vol_var__Float32x, vol_var_char)) var__Float32x__attribute__ ((unused));
>>>>       |                                                           ^~~~~~~~~~~~~
>>>> .../math/test-tgmath3-atan2.c:855:64: note: previous declaration of 'var__Float32x' with type '_Float32x'
>>>>   855 |   extern typeof (atan2 (vol_var__Float32x, vol_var__Float32x)) var__Float32x __attribute__ ((unused));
>>>>       |                                                                ^~~~~~~~~~~~~
>>>>
>>>
>>> Which gcc version are you using? I recall that we saw some issues on some
>>> targets when _Float32x was added, but I didn't see any build failures on
>>> master with recent gcc.  I think we still might have some issues with
>>> older gcc trying to build recent glibc, I fixed some issues on some targets
>>> but I did check all of them.
>>
>>  The version used still quoted above along with my reservation, but the 
>> whole point of my recent Alpha/Linux activity has been implementing a 
>> workaround in GCC for an architectural misfeature with non-BWX Alpha 
>> microarchitectures (that is EV4, EV45, EV5) so that support for this 
>> hardware is retained in the Linux kernel.  Which means I'll be using GCC 
>> 15 master really soon now.
> 
>  Scratch it, I got the MIPS and the Alpha port confused here, sorry.  I 
> guess ETOOMANYCONTEXTS happened here.
> 
>  I won't upgrade the MIPS compiler beyond GCC 13, because soon afterwards
> a new port maintainer was appointed by the GCC Steering Committee despite 
> my objection and shortly changes started being fast-tracked to the port 
> without proper review, so I don't trust the MIPS compiler anymore.  I can 
> upgrade to the GCC 13 branch though and report back.

Sorry, it was not clear which version you saw the _Float32x issue, was it 
with gcc 13 or with gcc 15? 

For gcc 13/14 I have multiple builds with recent glibc and I haven't see 
any issue on multiple MIPS ABIs, so it might something with master branch.
I don't keep track as often as with gcc release branches.


More information about the Libc-alpha mailing list