https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119014
--- Comment #8 from Vincent Lefèvre <vincent-gcc at vinc17 dot net> --- (In reply to Jakub Jelinek from comment #6) > I don't think that is true. Indeed, it seems that I did some mistake when searching the standard, which is a bit contradictory about the case FLT_EVAL_METHOD = 0. In 5.2.5.3.2, this case expresses the fact that there is no extended precision for any floating type (so, the safest behavior), but this is no longer true with Annex H! Note that extended precision brings confusion for users, with more risks of issues than benefits: see bug 323 and its 103 duplicates! IMHO, it should really be avoided by default.