FreeBSD-src - Raptor Engineering's fork of pfsense FreeBSD src with pfSense changes

	Commit message (Collapse)	Author	Age	Files	Lines
*	Fix EABI unwind function declarations to match the function definitions.	ian	2014-07-22	1	-2/+2
\| \| \| \| \|	The mismatch was noticed by clang, when using it to compile the in-tree gcc and libstdc++.
*	Make libsupc++'s __cxa_call_terminate() prototype consistent with the	dim	2013-06-29	1	-1/+1
\| \| \| \| \| \| \|	definition. Submitted by: dt71@gmx.com MFC after: 3 days
*	Allow the unwind functions int libgcc_s to interact correctly with libthr.	andrew	2013-02-04	1	-9/+11
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	_Unwind_ForcedUnwind in libgcc_s takes as one of it's parameters a stop function to tell it when to stop unwinding. One of the stop function's parameters is a _Unwind_Exception_Class. On most architectures this is an int64_t, however on ARM EABI the gcc developers have made this a char array with 8 items. While both of these take the same space they are passed into the stop function differently, an int64_t is passed in in registers r2 and r3, while the char[8] is passed in as a pointer to the first item in register r2. Because libthr expects the value to be an int64_t we would get incorrect results when it passes a function that take an int64_t but libgcc passes in a pointer to a char array including crashing. The fix is to update libgcc_s to make it pass an int64_t to the stop function and to libstdc++ as it expects _Unwind_Exception_Class to be an array.
*	GCC 4.2.0 release C++ standard library and runtime support code.	kan	2007-05-19	1	-13/+93
\|
*	Gcc 3.4.2 20040728 C++ support bits.	kan	2004-07-28	1	-7/+7
\|
*	Gcc 3.3.1-pre 2003-07-11 C++ support bits.	kan	2003-07-11	1	-1/+1
\|
*	Gcc 3.1.0 pre-release's C++ support bits from the FSF anoncvs repo	obrien	2002-05-28	1	-0/+171
	on 9-May-2002 15:57:15 EDT.