167961f6dc
To be compatible with GCC if soft floating point is in effect any FPU specified is effectively ignored, eg, -mfloat-abi=soft -fpu=neon If any floating point features which require FPU hardware are enabled they must be disable. There was some support for doing this for NEON, but it did not handle VFP, nor did it prevent the backend from emitting the build attribute Tag_FP_arch describing the generated code as using the floating point hardware if a FPU was specified (even though soft float does not use the FPU). Disabling the hardware floating point features for targets which are compiling for soft float has meant that some tests which were incorrectly checking for hardware support also needed to be updated. In such cases, where appropriate the tests have been updated to check compiling for soft float and a non-soft float variant (usually softfp). This was usually because the target specified in the test defaulted to soft float. Differential Revision: https://reviews.llvm.org/D42569 llvm-svn: 325492 |
||
|---|---|---|
| .. | ||
| AArch64.cpp | ||
| AArch64.h | ||
| ARM.cpp | ||
| ARM.h | ||
| Mips.cpp | ||
| Mips.h | ||
| PPC.cpp | ||
| PPC.h | ||
| RISCV.cpp | ||
| RISCV.h | ||
| Sparc.cpp | ||
| Sparc.h | ||
| SystemZ.cpp | ||
| SystemZ.h | ||
| X86.cpp | ||
| X86.h | ||