about summary refs log tree commit diff
path: root/Makeconfig
diff options
context:
space:
mode:
authorMike Frysinger <vapier@gentoo.org>2015-07-22 23:11:10 -0400
committerMike Frysinger <vapier@gentoo.org>2015-07-23 03:28:53 -0400
commit3840aabcd5b482b5e6cf5b204d1019ea0ddc9827 (patch)
tree3ad8cdecf3b9fd7098ad3fdc4419bac467ef247d /Makeconfig
parent992f71ddd34b0caf8fb04bc99e4bab8cb7badf83 (diff)
downloadglibc-3840aabcd5b482b5e6cf5b204d1019ea0ddc9827.tar.gz
glibc-3840aabcd5b482b5e6cf5b204d1019ea0ddc9827.tar.xz
glibc-3840aabcd5b482b5e6cf5b204d1019ea0ddc9827.zip
conform/linknamespace: whitelist matherrf/matherrl
glibc supports the deprecated matherr hook for math error reporting.  The
conform tests take this into consideration and whitelist this symbol when
running linknamespace tests.

The ia64 libm code has long provided two additional hooks in this space:
	matherrf (for floats)
	matherrl (for long doubles)

Which causes the conform tests to fail with chains that all look like:
	[initial] __atan2 ->
	[libm.a(e_atan2.o)] __libm_error_support ->
	[libm.a(libm_error.o)] matherrf

We can't (losslessly) redirect existing usage of these funcs to matherr
because the structure passed in is different -- matherr uses a struct with
doubles while matherrf/matherrl use floats and long doubles respectively.
Plus, this has been part of the exported ABI since glibc-2.2.3, so it
doesn't feel right to change it so late.

Until we get around to obsoleting matherr entirely, whitelist these two
additional ia64 symbols.
Diffstat (limited to 'Makeconfig')
0 files changed, 0 insertions, 0 deletions