No description

Jingwei Zhang 90be6c5fc5 The nextafter functions use the wrong next representable value ... From C99 standard: “The nextafter functions determine the next representable value, in the type of the function, after x in the direction of y, where x and y are first converted to the type of the function”. The next representable value of 0.0 in direction of -1.0 is -4.9406564584124654e-324, not 0.0. Similar thing holds for nextafterf, nextafterl, nexttowardf, nexttoward, and nexttowardl. The tests pass either way, since the error is within the tolerance, but how it is written is wrong. Change-Id: I1338eeffe3de8031a48f46e1b07146bc07dc2f0a Signed-off-by: Jingwei Zhang <jingwei.zhang@intel.com> Signed-off-by: Mingwei Shi <mingwei.shi@intel.com>		2014-09-19 00:50:00 +08:00
benchmarks	Add benchmarks for pthread_rw_locks	2014-09-16 18:02:30 +01:00
libc	Update kernel uapi headers to v3.16.1.	2014-09-17 17:05:17 -07:00
libdl	Turn on -Wunused and fix the mistakes it uncovers.	2014-06-03 15:22:34 -07:00
libm	Get new coshl, sinhl, and tanhl implementations from upstream.	2014-09-12 16:09:40 -07:00
libstdc++	Fix filename in comment in cmath	2014-09-14 16:41:31 +02:00
linker	Temporary disable DL_WARNs for unused DT_*	2014-09-17 16:46:40 -07:00
tests	The nextafter functions use the wrong next representable value	2014-09-19 00:50:00 +08:00
.gitignore	Merge memory checking functionality from sandbox	2010-02-16 11:43:18 -08:00
ABI-bugs.txt	PTHREAD_KEYS_MAX cleanup.	2013-12-12 12:51:08 -08:00
Android.mk	Remove the simulator target from all makefiles.	2011-07-11 22:11:41 -07:00
CleanSpec.mk	Make jemalloc the default choice.	2014-07-11 11:01:30 -07:00
HACKING.txt	Rewrite syslog(3) to use Android logging.	2014-07-21 16:56:48 -07:00