https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119014
--- Comment #12 from Vincent Lefèvre <vincent-gcc at vinc17 dot net> --- (In reply to Jakub Jelinek from comment #9) > The reason for extended precision by default for _Float16 (and __bf16) on > x86 (and most of other targets, I think RISC-V is an exception) is lack of > hw support, same reason as for i387 extended precision. A user who wants something fast on x86 (or similar targets) should use float or double: that's explicit, no surprises. The main goal of _Float16 on x86 is to analyze what would happen for a hardware dedicated to _Float16; in this case, it is very important not to get a larger precision.
