Searched refs:VFP (Results 1 – 25 of 53) sorted by relevance
123
/external/llvm/test/MC/ARM/ |
D | vfp-aliases-diagnostics.s | 34 @ CHECK: error: VFP/Neon double precision register expected 37 @ CHECK: error: VFP/Neon double precision register expected 40 @ CHECK: error: VFP/Neon double precision register expected 43 @ CHECK: error: VFP/Neon double precision register expected 46 @ CHECK: error: VFP/Neon single precision register expected 49 @ CHECK: error: VFP/Neon single precision register expected 52 @ CHECK: error: VFP/Neon single precision register expected 55 @ CHECK: error: VFP/Neon single precision register expected 59 @ CHECK: error: VFP/Neon single precision register expected 62 @ CHECK: error: VFP/Neon single precision register expected [all …]
|
D | single-precision-fp.s | 10 @ CHECK-ERRORS: error: instruction requires: double precision VFP 12 @ CHECK-ERRORS: error: instruction requires: double precision VFP 14 @ CHECK-ERRORS: error: instruction requires: double precision VFP 16 @ CHECK-ERRORS: error: instruction requires: double precision VFP 18 @ CHECK-ERRORS: error: instruction requires: double precision VFP 29 @ CHECK-ERRORS: error: instruction requires: double precision VFP 31 @ CHECK-ERRORS: error: instruction requires: double precision VFP 33 @ CHECK-ERRORS: error: instruction requires: double precision VFP 35 @ CHECK-ERRORS: error: instruction requires: double precision VFP 37 @ CHECK-ERRORS: error: instruction requires: double precision VFP [all …]
|
D | neon-mov-vfp.s | 1 …nknown -show-encoding -mattr=-neon < %s 2>&1 | FileCheck %s --check-prefix=VFP --check-prefix=CHECK 2 …nknown -show-encoding -mattr=-neon < %s 2>&1 | FileCheck %s --check-prefix=VFP --check-prefix=CHECK 14 @ VFP-DAG: error: instruction requires: NEON 15 @ VFP-DAG: error: instruction requires: NEON 26 @ VFP-DAG: error: instruction requires: NEON 27 @ VFP-DAG: error: instruction requires: NEON
|
D | eh-directive-integrated-test.s | 19 @ restore the general-purpose and VFP registers.
|
D | eh-directive-vsave.s | 6 @ The .vsave directive records the VFP registers which are pushed to the
|
/external/llvm/test/CodeGen/ARM/ |
D | fpconv.ll | 1 ; RUN: llc -mtriple=arm-eabi -mattr=+vfp2 %s -o - | FileCheck %s --check-prefix=CHECK-VFP 5 ;CHECK-VFP-LABEL: f1: 6 ;CHECK-VFP: vcvt.f32.f64 15 ;CHECK-VFP-LABEL: f2: 16 ;CHECK-VFP: vcvt.f64.f32 25 ;CHECK-VFP-LABEL: f3: 26 ;CHECK-VFP: vcvt.s32.f32 35 ;CHECK-VFP-LABEL: f4: 36 ;CHECK-VFP: vcvt.u32.f32 45 ;CHECK-VFP-LABEL: f5: [all …]
|
D | no-fpu.ll | 4 …N: llc < %s -mtriple=armv7-none-gnueabi -mattr=-neon,+vfp2 | FileCheck --check-prefix=NONEON-VFP %s 22 ; Likewise with VFP instructions. 29 ; NONEON-VFP: vmov 30 ; NONEON-VFP: vmul.f64
|
D | select.ll | 4 ; RUN: | FileCheck %s --check-prefix=CHECK-VFP 67 ;CHECK-VFP-LABEL: f7: 68 ;CHECK-VFP: vmovmi 101 ; CHECK-VFP-LABEL: f9:
|
D | 2013-04-16-AAPCS-C5-vs-VFP.ll | 7 ;Co-Processor register candidates may be either in VFP or in stack, so after 8 ;all VFP are allocated, stack is used. We can use stack without GPR allocation
|
D | vector-extend-narrow.ll | 23 ; Note: vld1 here is reasonably important. Mixing VFP and NEON 52 ; Note: vld1 here is reasonably important. Mixing VFP and NEON
|
D | 2013-04-16-AAPCS-C4-vs-VFP.ll | 6 ;Co-Processor register candidates may be either in VFP or in stack, so after 7 ;all VFP are allocated, stack is used. We can use stack without GPR allocation
|
D | 2013-04-21-AAPCS-VA-C.1.cp.ll | 2 ;Note: There are no VFP CPRCs in a variadic procedure.
|
D | vfp-regs-dwarf.ll | 10 ; the layout of the VFP registers correctly. The fact that the numbers are
|
/external/llvm/lib/Target/ARM/ |
D | ARMInstrVFP.td | 1 //===-- ARMInstrVFP.td - VFP support for ARM ---------------*- tablegen -*-===// 10 // This file describes the ARM VFP instruction set. 97 // Some single precision VFP instructions may be executed on both NEON and VFP 111 // Some single precision VFP instructions may be executed on both NEON and VFP 159 // Some single precision VFP instructions may be executed on both NEON and 160 // VFP pipelines. 172 // Some single precision VFP instructions may be executed on both NEON and 173 // VFP pipelines. 185 // Some single precision VFP instructions may be executed on both NEON and 186 // VFP pipelines. [all …]
|
D | ARMFPUName.def | 20 ARM_FPU_NAME("vfp", VFP)
|
D | ARM.td | 76 // Cyclone has preferred instructions for zeroing VFP registers, which can 82 // play nicely with other VFP / NEON instructions, and it's generally better 85 "Disable VFP / NEON MAC instructions">;
|
D | ARMInstrFormats.td | 125 def VFPDomain : Domain<1>; // Instructions in VFP domain only 127 def VFPNeonDomain : Domain<3>; // Instructions in both VFP & Neon domains 128 def VFPNeonA8Domain : Domain<5>; // Instructions in VFP & Neon under A8 1405 // ARM VFP Instruction templates. 1408 // Almost all VFP instructions are predicable. 1420 let DecoderNamespace = "VFP"; 1436 let DecoderNamespace = "VFP"; 1447 // ARM VFP addrmode5 loads and stores 1469 // Loads & stores operate on both NEON and VFP pipelines. 1494 // Loads & stores operate on both NEON and VFP pipelines. [all …]
|
/external/boringssl/src/crypto/chacha/ |
D | chacha_vec_arm_generate.go | 133 # EABI attribute 28 sets whether VFP register arguments were used to build this 136 # VFP arguments.
|
/external/elfutils/src/tests/ |
D | run-addrcfi.sh | 2542 VFP reg256 (d0): undefined 2543 VFP reg257 (d1): undefined 2544 VFP reg258 (d2): undefined 2545 VFP reg259 (d3): undefined 2546 VFP reg260 (d4): undefined 2547 VFP reg261 (d5): undefined 2548 VFP reg262 (d6): undefined 2549 VFP reg263 (d7): undefined 2550 VFP reg264 (d8): same_value 2551 VFP reg265 (d9): same_value [all …]
|
D | run-readelf-A.sh | 51 ABI_VFP_args: VFP registers
|
/external/llvm/test/CodeGen/Thumb2/ |
D | float-intrinsics-float.ll | 3 …k %s -check-prefix=CHECK -check-prefix=HARD -check-prefix=DP -check-prefix=VFP -check-prefix=FP-A… 123 ; VFP: lsrs [[REG:r[0-9]+]], r{{[0-9]+}}, #31 124 ; VFP: bfi r{{[0-9]+}}, [[REG]], #31, #1
|
D | float-intrinsics-double.ll | 3 …k %s -check-prefix=CHECK -check-prefix=HARD -check-prefix=DP -check-prefix=VFP -check-prefix=FP-A… 125 ; VFP: lsrs [[REG:r[0-9]+]], r3, #31 126 ; VFP: bfi r1, [[REG]], #31, #1
|
/external/llvm/lib/CodeGen/ |
D | SplitKit.cpp | 397 ValueForcePair &VFP = Values[std::make_pair(RegIdx, ParentVNI->id)]; in forceRecompute() local 398 VNInfo *VNI = VFP.getPointer(); in forceRecompute() 403 VFP.setInt(true); in forceRecompute() 413 VFP = ValueForcePair(nullptr, true); in forceRecompute() 846 ValueForcePair VFP = Values.lookup(std::make_pair(RegIdx, ParentVNI->id)); in transferValues() local 847 if (VNInfo *VNI = VFP.getPointer()) { in transferValues() 855 if (VFP.getInt()) { in transferValues()
|
/external/libcxxabi/src/Unwind/ |
D | UnwindRegistersSave.S | 297 @ however this is very hard to do for VFP registers because it is unknown 299 @ Instead, VFP registers are demand saved by logic external to unw_getcontext. 362 @ VFP and iwMMX instructions are only available when compiling with the flags
|
/external/clang/include/clang/Basic/ |
D | BuiltinsARM.def | 44 // VFP
|
123