On Wed, 18 May 2016, Joseph Myers wrote: > But why do you need to force that? If the instructions follow IEEE > semantics including for exceptions and rounding modes, then X OP Y > computed directly with binary16 arithmetic has the same value as results > from promoting to binary32, doing binary32 arithmetic and converting back > to binary16, for OP in + - * /. (Double-rounding problems can only occur
I should say: this is not the case for fma - (__fp16) fmaf (a, b, c) need not be the same as fmaf16 (a, b, c) for fp16 values a, b, c - but I think you should use the standard instruction name there as well - if the instruction is a fused multiply-add on binary16, it should be described as such. -- Joseph S. Myers jos...@codesourcery.com
