On Apr 14, 2022, Segher Boessenkool <seg...@kernel.crashing.org> wrote:
> 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. Sorry, that message from last year was an unfounded suspicion of mine based on incorrect information. Indeed, -mcpu=power9 combined with -mno-vsx raise an error. The relevant fact, described in yesterday's message, is that -mfloat128 is not enabled by default, even with -mcpu=power9, except on target variants that define TARGET_FLOAT128_ENABLE_TYPE to nonzero. As you stated, its overall default is zero (though GNU/Linux overrides it to nonzero), so the existing tests do not conform with the machine's defaults in assuming -mfloat128 is enabled by -mcpu=power9. Would you please reconsider your assessment, disregarding my incorrect and irrelevant suspicions from last year, and instead taking the updated and corrected information about float128 defaults into account? Thanks, >> 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. Yup, this was another incorrect suspicion of mine, based on another piece of irrelevant information. -- 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>
