Hi! On Sat, Apr 17, 2021 at 06:19:02AM -0300, Alexandre Oliva wrote: > On Apr 12, 2021, Segher Boessenkool <seg...@kernel.crashing.org> wrote: > > 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,
Yes, that is a problem. None of our testcases are set up for compilers with weird defaults (and this is not specific to rs6000). I do not want to change many thousands of test cases to not use defaults anymore, to specify everything everywhere instead :-( This would make things more unmaintainable than they already are. > or the very old default CPU. powerpc-linux uses 603, introduced at the same time as 604 (in 1994), which is what vxworks appears to use. It has all the same features. > 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. GCC for PowerPC does not currently support IEEE QP float on CPUs without VSX. Other than that, it should work (but no doubt there still are problems). Segher
