bionic.git - Android's bionic

	Commit message (Collapse)	Author	Age	Files	Lines
*	Clean up more recursive FORTIFY_SOURCE calls	Nick Kralevich	2013-12-18	1	-0/+2
\| \| \| \| \| \| \| \| \| \|	Don't use FORTIFY_SOURCE on functions which implement FORTIFY_SOURCE, to avoid infinite recursion problems. The previous patch only addressed one of the problems. Bug: 12216860 Change-Id: I6f30ae7cb5b481be9942add18182ea4839d348a6
*	Avoid confusing "read prevented write" log messages.	Elliott Hughes	2013-10-15	1	-6/+6
\| \| \| \| \| \|	Moving to a "function: message" style avoids ambiguity. Change-Id: If9d590e50265c61725d3673bd03796e65edd2d5e
*	Fix x86_64 build, clean up intermediate libraries.	Elliott Hughes	2013-10-09	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	The x86_64 build was failing because clone.S had a call to __thread_entry which was being added to a different intermediate .a on the way to making libc.so, and the linker couldn't guarantee statically that such a relocation would be possible. ld: error: out/target/product/generic_x86_64/obj/STATIC_LIBRARIES/libc_common_intermediates/libc_common.a(clone.o): requires dynamic R_X86_64_PC32 reloc against '__thread_entry' which may overflow at runtime; recompile with -fPIC This patch addresses that by ensuring that the caller and callee end up in the same intermediate .a. While I'm here, I've tried to clean up some of the mess that led to this situation too. In particular, this removes libc/private/ from the default include path (except for the DNS code), and splits out the DNS code into its own library (since it's a weird special case of upstream NetBSD code that's diverged so heavily it's unlikely ever to get back in sync). There's more cleanup of the DNS situation possible, but this is definitely a step in the right direction, and it's more than enough to get x86_64 building cleanly. Change-Id: I00425a7245b7a2573df16cc38798187d0729e7c4
*	Make error messages even better!	Nick Kralevich	2013-10-04	1	-1/+1
\| \| \| \|	Change-Id: I72bd1eb1d526dc59833e5bc3c636171f7f9545af
*	FORTIFY_SOURCE: emphasize prevention in error messages.	Nick Kralevich	2013-10-04	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \|	FORTIFY_SOURCE prevents buffer overflows from occurring. However, the error message often implies that we only detect it, not prevent it. Bring more clarity to the error messages by emphasizing prevention over detection. Change-Id: I5f3e1478673bdfc589e6cc4199fce8e52e197a24
*	Use __predict_false on some fortify methods.	Nick Kralevich	2013-05-02	1	-1/+1
\| \| \| \| \| \| \|	Give the compiler some hints that these error conditions are unlikely to occur in practice. Change-Id: Ifaf7322a12120ef663c8315c1a18c2dcbe4bda23
*	Clean up internal libc logging.	Elliott Hughes	2013-03-15	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \|	We only need one logging API, and I prefer the one that does no allocation and is thus safe to use in any context. Also use O_CLOEXEC when opening the /dev/log files. Move everything logging-related into one header file. Change-Id: Ic1e3ea8e9b910dc29df351bff6c0aa4db26fbb58
*	clean up FORTIFY_SOURCE handling.	Nick Kralevich	2012-12-04	1	-4/+2
\| \| \| \| \| \|	Avoid duplicating huge chunks of code. Change-Id: Id6145cdfce781c5ffba2abaaa79681d25a7ab28f
*	Move the FORTIFY_SOURCE helpers over to .cpp.	Elliott Hughes	2012-10-22	1	-0/+53
	Change-Id: Ib5067d51b983cac7760c975becce7fe2408ead04