summary refs log tree commit diff
path: root/manual/lang.texi
diff options
context:
space:
mode:
authorTulio Magno Quites Machado Filho <tuliom@linux.ibm.com>2019-10-20 16:00:30 -0500
committerGabriel F. T. Gomes <gabrielftg@linux.ibm.com>2019-12-27 15:02:10 -0300
commit1ef9b6e0bf1268050e74087c4f6bd056263a28c7 (patch)
tree3b3f7905c03c4890473ab9da3e7fdc5dbb42241e /manual/lang.texi
parent863d775c481704baaa41855fc93e5a1ca2dc6bf6 (diff)
downloadglibc-1ef9b6e0bf1268050e74087c4f6bd056263a28c7.tar.gz
glibc-1ef9b6e0bf1268050e74087c4f6bd056263a28c7.tar.xz
glibc-1ef9b6e0bf1268050e74087c4f6bd056263a28c7.zip
Do not redirect calls to __GI_* symbols, when redirecting to *ieee128
On platforms where long double has IEEE binary128 format as a third
option (initially, only powerpc64le), many exported functions are
redirected to their __*ieee128 equivalents.  This redirection is
provided by installed headers such as stdio-ldbl.h, and is supposed to
work correctly with user code.

However, during the build of glibc, similar redirections are employed,
in internal headers, such as include/stdio.h, in order to avoid extra
PLT entries.  These redirections conflict with the redirections to
__*ieee128, and must be avoided during the build.  This patch protects
the second redirections with a test for __LONG_DOUBLE_USES_FLOAT128, a
new macro that is defined to 1 when functions that deal with long double
typed values reuses the _Float128 implementation (this is currently only
true for powerpc64le).

Tested for powerpc64le, x86_64, and with build-many-glibcs.py.

Co-authored-by: Gabriel F. T. Gomes <gabrielftg@linux.ibm.com>
Reviewed-by: Florian Weimer <fweimer@redhat.com>
Diffstat (limited to 'manual/lang.texi')
0 files changed, 0 insertions, 0 deletions