https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106117
--- Comment #4 from John McCall <rjmccall at gmail dot com> --- Ah, thank you, we weren't aware of -fexcess-precision=16. If that's the precedent, we can certainly follow it. The idea around "16" was to make it clear that this just affects _Float16? If the option were named -fexcess-precision=none, then I suppose someone who had started passing it years ago to prevent float/double promotion on i386 would now unintentionally be affected by it for _Float16. Put another way, there's an implicit assumption in the re-use of a single option that targets will have a linear history of support for more floating point types, such that there's only one kind of emulation in use at once.
