86ac3a98b5
We don't actually detect whether the compiler can create Neon code or provides Neon intrinsics. Most of them do, so that test would be mostly moot. We removed the detection previously because we couldn't automatically enable Neon due to leakage of instructions outside the areas protected at runtime. Instead, we rely on the mkspec properly passing the necessary flags that enable Neon support. This commit does not change that. All it does is verify whether the arch detection found "neon" as part of the target CPU features. In other words, it moves the test that was in simd.prf to configure. It does fix the Neon detection in configure.exe, which was always failing for trying to run a test that didn't exist (config.tests/unix/neon). Change-Id: Id561dfb2db7d3dca7b8c29afef63181693bdc0aa Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com> |
||
|---|---|---|
| .. | ||
| configure_pch.h | ||
| configure.pro | ||
| configureapp.cpp | ||
| configureapp.h | ||
| environment.cpp | ||
| environment.h | ||
| main.cpp | ||
| Makefile.mingw | ||
| Makefile.win32 | ||
| tools.cpp | ||
| tools.h | ||