On Jul 11, 2024, Andreas Schwab <sch...@suse.de> wrote: > On Jul 11 2024, Jonathan Wakely wrote: >> On Thu, 11 Jul 2024 at 14:21, Alexandre Oliva <ol...@adacore.com> wrote: >>> >>> >>> Having observed failures of these two tests on yet another aarch64 >>> operating system, and having concluded that the conditions that >>> trigger the problem ought to be present on all aarch64 targets, I'm >>> now matching any aarch64 target_os to enable the workaround. >> >> That's concerning, aarch64-unknown-linux-gnu with glibc should work OK >> for float128_t, because aarch64 already has 128-bit long double, so >> there's no good reason that float128_t wouldn't work. What are the >> conditions that trigger the problem?
> Both tests run sucessfully on aarch64-linux. Thanks, I stand corrected. I got the right answer for the wrong question. All aarch64 have '# define USE_LIB_FAST_FLOAT 1', but that won't limit the precision of from_char for 128-bit float types when strtold et al can be used for the conversion. Patch withdrawn, on the grounds of... general failure to engage brain ;-D -- Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/ Free Software Activist GNU Toolchain Engineer More tolerance and less prejudice are key for inclusion and diversity Excluding neuro-others for not behaving ""normal"" is *not* inclusive
