mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-11-23 11:13:28 +01:00
1031830a08
r361845 changed the way we handle "D16" vs. "D32" targets; there used to be a negative "d16" which removed instructions from the instruction set, and now there's a "d32" feature which adds instructions to the instruction set. This is good, but there was an oversight in the implementation: the behavior of VFPv2 was changed. In particular, the "vfp2" feature was changed to imply "d32". This is wrong: VFPv2 only supports 16 D registers. In practice, this means if you specify -mfpu=vfpv2, the compiler will generate illegal instructions. This patch gets rid of "vfp2d16" and "vfp2d16sp", and fixes "vfp2" and "vfp2sp" so they don't imply "d32". Differential Revision: https://reviews.llvm.org/D67375 llvm-svn: 372186
21 lines
927 B
LLVM
21 lines
927 B
LLVM
; RUN: llc -mtriple=armv7-none-eabi -mattr=-neon,-vfp2sp %s -o - | FileCheck %s -check-prefixes=COMMON,NOVFP
|
|
; RUN: llc -mtriple=armv7-none-eabi -mattr=+neon %s -float-abi=hard -o - | FileCheck %s -check-prefixes=COMMON,VFP
|
|
|
|
; The intent here is to test "X", which says that any operand whatsoever is allowed.
|
|
; Using this mechanism, we want to test toggling allocating GPR or SPR registers
|
|
; depending on whether the float registers are available. Thus, the mnemonic is
|
|
; totally irrelevant here, which is why we use FOO and also comment it out using "@"
|
|
; to avoid assembler errors.
|
|
|
|
; Note that this kind of IR can be generated by a function such as:
|
|
; void f1(float f) {asm volatile ("@FOO $0, $0" : : "X" (f));}
|
|
|
|
define arm_aapcs_vfpcc void @func(float %f) {
|
|
; COMMON-LABEL: func
|
|
; NOVFP: FOO r0, r0
|
|
; VFP: FOO s0, s0
|
|
entry:
|
|
call void asm sideeffect "@FOO $0, $0", "X" (float %f) nounwind
|
|
ret void
|
|
}
|