https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114347
--- Comment #9 from Hongtao Liu <liuhongt at gcc dot gnu.org> --- (In reply to Richard Biener from comment #7) > (In reply to Jakub Jelinek from comment #6) > > You can use -fexcess-precision=16 if you don't want treating _Float16 and > > __bf16 as having excess precision. With excess precision, I think the above > > behavior is correct. > > You'd need (int) (__bf16) 257.0bf16 to get 256 even with excess precision. > > Ah, -fexcess-precision=16 doesn't seem to be documented though (how does > this influence long double handling then?) Oh, I forgot to add that in invoke.texi. -fexcess-precision=16 doesn't impact types with precision > 16. And it's not compatible with -mfpmath=387.
