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. -- Andreas Schwab, SUSE Labs, sch...@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."
