On Apr 17, 2021, Alexandre Oliva <ol...@adacore.com> wrote: > On Apr 12, 2021, Segher Boessenkool <seg...@kernel.crashing.org> wrote: >> Hi! >> Sorry for the late answer.
Likewise :-) >> 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. My supposition was wrong. It turned out to be just because in vxworks.h, for TARGET_VXWORKS7, there's: #define TARGET_FLOAT128_ENABLE_TYPE 0 This disables TARGET_FLOAT128_TYPE by default, and causes the warning to be issued when -mfloat128 is explicitly enabled. So ping https://gcc.gnu.org/pipermail/gcc-patches/2021-April/567630.html upthread, and expect 3 new patches related with -mfloat128 momentarily. -- Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/ Free Software Activist GNU Toolchain Engineer Disinformation flourishes because many people care deeply about injustice but very few check the facts. Ask me about <https://stallmansupport.org>
