aboutsummaryrefslogtreecommitdiff
path: root/inet/Versions
diff options
context:
space:
mode:
authorGabriel F. T. Gomes <gabriel@inconstante.eti.br>2018-06-10 22:42:34 -0300
committerGabriel F. T. Gomes <gabriel@inconstante.eti.br>2018-12-07 17:28:26 -0200
commit10446f5d9f2cf4d91c8ae483fd2b5470242ae2a1 (patch)
tree68e631fca5b65a44e28f5b3791ff2e9b8fc56a25 /inet/Versions
parent45f33aac78e86d0f23c74a207295f3c7a77a94c0 (diff)
downloadglibc-10446f5d9f2cf4d91c8ae483fd2b5470242ae2a1.tar
glibc-10446f5d9f2cf4d91c8ae483fd2b5470242ae2a1.tar.gz
glibc-10446f5d9f2cf4d91c8ae483fd2b5470242ae2a1.tar.bz2
glibc-10446f5d9f2cf4d91c8ae483fd2b5470242ae2a1.zip
Prepare vfscanf to use __strtof128_internal
On powerpc64le, long double can currently take two formats: the same as double (-mlong-double-64) or IBM Extended Precision (default with -mlong-double-128 or explicitly with -mabi=ibmlongdouble). The internal implementation of scanf-like functions is aware of these possibilites and, based on the format in use, properly calls __strtold_internal or __strtod_internal, saving the return to a variable of type double or long double. When library support for TS 18661-3 was added to glibc, a new function, __strtof128_internal, was added to enable reading of floating-point values with IEEE binary128 format into the _Float128 type. Now that powerpc64le is getting support for its third long double format, and taking into account that this format is the same as the format of _Float128, this patch extends __vfscanf_internal and __vfwscanf_internal to call __strtof128_internal or __wcstof128_internal when appropriate. The result gets saved into a variable of _Float128 type. Tested for powerpc64le.
Diffstat (limited to 'inet/Versions')
0 files changed, 0 insertions, 0 deletions