On Tue, 17 May 2016, Matthew Wahab wrote: > In some tests, there are unavoidable differences in precision when > calculating the actual and the expected results of an FP16 operation. A > new support function CHECK_FP_BIAS is used so that these tests can check > for an acceptable margin of error. In these tests, the tolerance is > given as the absolute integer difference between the bitvectors of the > expected and the actual results.
As far as I can see, CHECK_FP_BIAS is only used in the following patch, but there is another bias test in vsqrth_f16_1.c in this patch. Could you clarify where the "unavoidable differences in precision" come from? Are the results of some of the new instructions not fully specified, only specified within a given precision? (As far as I can tell the existing v8 instructions for reciprocal and reciprocal square root estimates do have fully defined results, despite being loosely described as esimtates.) -- Joseph S. Myers jos...@codesourcery.com
