diff options
author | Gabriel F. T. Gomes <gabriel@inconstante.eti.br> | 2018-06-05 16:54:40 -0300 |
---|---|---|
committer | Paul E. Murphy <murphyp@linux.vnet.ibm.com> | 2020-02-28 08:20:02 -0600 |
commit | d96723744332c22a4202a0505a3814cd950bc05d (patch) | |
tree | 528042fe6d9e2dbf7a280b201cb051dad8c2f855 /localedata/tr_TR.UTF-8.in | |
parent | f1a166b0d7af9aa0f4021f67ed8ed496ee2c8b84 (diff) | |
download | glibc-d96723744332c22a4202a0505a3814cd950bc05d.tar.gz glibc-d96723744332c22a4202a0505a3814cd950bc05d.tar.xz glibc-d96723744332c22a4202a0505a3814cd950bc05d.zip |
ldbl-128ibm-compat: Provide nexttoward functions
The functions in the nexttoward family are special, in the sense that they always have a long double argument, regardless of their suffix (i.e.: nexttowardf and nexttoward have a long double argument, besides the float and double arguments). On top of that, they are also special because nexttoward functions are not part of the _FloatN API, hence __nexttowardf128 do not exist. This patch adds 4 new function implementations for the new long double format: __nexttoward_to_ieee128 __nexttowardf_to_ieee128 __nexttowardieee128 (as an alias to __nextafterieee128) Likewise, rename "long double" "_Float128" in shared ldbl-128 files to ensure correct type is used irrespective of ABI switches. Thank you to those who helped out with this patch: Co-Authored-By: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
Diffstat (limited to 'localedata/tr_TR.UTF-8.in')
0 files changed, 0 insertions, 0 deletions