diff options
author | John-Mark Bell <jmb@netsurf-browser.org> | 2015-11-28 22:37:28 +0000 |
---|---|---|
committer | John-Mark Bell <jmb@netsurf-browser.org> | 2015-11-28 22:37:28 +0000 |
commit | 9b4182fac113cd3481b81b3446c25eb40c26a5bb (patch) | |
tree | a6de73573edde841eca27ed1147c135b54681fa0 /sdk/recipes/patches/libcares | |
parent | 3e4f15d537df461c67e5b7ea1eddb807e3d006fb (diff) | |
download | toolchains-jmb/openssl-asm.tar.gz toolchains-jmb/openssl-asm.tar.bz2 |
OpenSSL: fully disable CPU feature detection.jmb/openssl-asm
It is unsafe to detect and use NEON or VFP instructions at
runtime in a binary built using default compiler options.
This is because the UnixLib runtime will only create and manage
floating point contexts if -mfloat-abi is set to "softfp" at
build time (which may occur automagically based on other
compiler switches such as -mfpu). This is further complicated
by the need to build a VFP-capable binary or else UnixLib will
enable its FPA support code instead.
Neither is desirable as FPA emulation will just be slower than
soft float and VFP will restrict the binary to ARMv6 or later
(and, even then, only certain CPUs) which would disappoint
all the users still running RiscPCs, A9Homes, or Iyonixes.
So disable this feature detection, until we can make
UnixLib enable support code based on runtime, rather than
(or, in addition to) compile-time, tests.
Diffstat (limited to 'sdk/recipes/patches/libcares')
0 files changed, 0 insertions, 0 deletions