Jason Evans d37d5adee4 Disable floating point code/linking when possible.
Unless heap profiling is enabled, disable floating point code and don't
link with libm.  This, in combination with e.g. EXTRA_CFLAGS=-mno-sse on
x64 systems, makes it possible to completely disable floating point
register use.  Some versions of glibc neglect to save/restore
caller-saved floating point registers during dynamic lazy symbol
loading, and the symbol loading code uses whatever malloc the
application happens to have linked/loaded with, the result being
potential floating point register corruption.
2013-12-05 23:01:50 -08:00
..
2012-05-01 11:32:11 -07:00
2012-03-13 16:31:41 -07:00
2012-10-08 18:04:49 -07:00
2012-02-28 16:50:47 -08:00
2012-04-21 21:27:46 -07:00
2012-03-02 15:59:45 -08:00
2011-11-01 20:48:31 -07:00
2012-10-09 15:21:46 -07:00
2012-03-07 16:19:19 -08:00
2013-10-19 23:48:40 -07:00
2013-10-24 18:25:19 -07:00