On Apr 12, 2021, Segher Boessenkool <seg...@kernel.crashing.org> wrote:
> Hi! > Sorry for the late answer. > On Fri, Apr 02, 2021 at 01:52:59PM -0300, Alexandre Oliva wrote: >> Several compile tests that use the __ieee128 type do not ensure it is >> defined. This patch adds -mfloat128 to their command lines, and >> disregards the warning that may be issued by it. > But they do make sure it is defined, they use -mcpu=power9 (etc.). What > is different in your setup that that does not work? I suppose it's either -mno-altivec -mno-vsx in our self-specs, or the very old default CPU. I imagine it's also possible that the issue, initially observed with GCC 10, is different or absent with the trunk. I started trying to figure out what led __ieee128 to not be enabled there, back then, but decided it was not so important, given that other tests used this flag explicitly, and that it wouldn't hurt to have it even if it wasn't always necessary. Now, if you tell me that, even with our implicit flags and old CPU selection, -mfloat128 should not be necessary to enable the __ieee128 type, I would be glad to dig further to try and fix the underlying bug. Thanks, -- Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/ Free Software Activist GNU Toolchain Engineer Vim, Vi, Voltei pro Emacs -- GNUlius Caesar
