diff options
author | Marius Hillenbrand <mhillen@linux.ibm.com> | 2020-12-01 15:36:34 +0100 |
---|---|---|
committer | Rich Felker <dalias@aerifal.cx> | 2020-12-03 19:07:24 -0500 |
commit | 738c4e945c1218559d36b83cbaba11459fad89c9 (patch) | |
tree | 58c66e2603b4c9c0ebde61ea79f6cf8dece07261 /compat/time32/ctime32.c | |
parent | 821083ac7b54eaa040d5a8ddc67c6206a175e0ca (diff) | |
download | musl-738c4e945c1218559d36b83cbaba11459fad89c9.tar.gz musl-738c4e945c1218559d36b83cbaba11459fad89c9.tar.bz2 musl-738c4e945c1218559d36b83cbaba11459fad89c9.tar.xz musl-738c4e945c1218559d36b83cbaba11459fad89c9.zip |
s390x: derive float_t from compiler or default to float
float_t should represent the type that is used to evaluate float
expressions internally. On s390x, float_t is currently set to double.
In contrast, the isa supports single-precision float operations and
compilers by default evaluate float in single precision, which
violates the C standard (sections 5.2.4.2.2 and 7.12 in C11/C17, to be
precise). With -fexcess-precision=standard, gcc evaluates float in
double precision, which aligns with the standard yet at the cost of
added conversion instructions.
gcc-11 will drop the special case to retrofit double precision
behavior for -fexcess-precision=standard so that __FLT_EVAL_METHOD__
will be 0 on s390x in any scenario.
To improve standards compliance and compatibility with future compiler
direction, this patch changes the definition of float_t to be derived
from the compiler's __FLT_EVAL_METHOD__.
Diffstat (limited to 'compat/time32/ctime32.c')
0 files changed, 0 insertions, 0 deletions