summaryrefslogtreecommitdiffstats
path: root/package/libasplib/libasplib.hash
diff options
context:
space:
mode:
authorYann E. MORIN <yann.morin.1998@free.fr>2015-12-26 17:05:42 +0100
committerThomas Petazzoni <thomas.petazzoni@free-electrons.com>2015-12-27 12:17:23 +0100
commitf52692ed64c64d24771e89f12b3db439247e28fc (patch)
tree0715cc5e459060b6cc98f03dfac4ce0ab3a23671 /package/libasplib/libasplib.hash
parentb64bcbf5f2cb066e8dd819a762f779d0015a68f7 (diff)
downloadbuildroot-f52692ed64c64d24771e89f12b3db439247e28fc.tar.gz
buildroot-f52692ed64c64d24771e89f12b3db439247e28fc.zip
arch/arm: add option to enable an optional VFP unit
Currently, the VFP selection for ARM is a little bit muddy: - some CPUs definitely do not have a VFP or NEON, - some CPUs definitely do have a VFP or NEON, - some CPUs may have a VFP or NEON. However, we currently conflate the availability of the VFP/NEON with the possibility to use them. Even is the user chooses a floating point strategy with a 'lower' solution (i.e. VFPv2 when a VFPv3 exists, or not using NEON when the CPU has it), some packages are still using the CPU-defined HW availaibility rather thean the usr's selection. Furthermore, for CPU that may have a VFP/NEON, there is no way for the user to actually specify that the HW is indeed available; the user can only specify the floating point strategy. This means that some packages or some package versions, like nodejs for example, can not be properly selected on some CPU cores, like Cortex-A9 which only may have a VFP. Like we have an option to enable an optional NEON unit, add a similar option to enable an optional VFP unit. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Diffstat (limited to 'package/libasplib/libasplib.hash')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud