llvm-project/llvm/test/CodeGen/ARM/2011-10-26-memset-with-neon.ll

; RUN: llc -march=arm -mcpu=cortex-a8 < %s | FileCheck %s

; Trigger multiple NEON stores.
; CHECK: vst1.64
; CHECK: vst1.64
define void @f_0_40(i8* nocapture %c) nounwind optsize {
entry:
  call void @llvm.memset.p0i8.i64(i8* %c, i8 0, i64 40, i32 16, i1 false)
  ret void
}

declare void @llvm.memset.p0i8.i64(i8* nocapture, i8, i64, i32, i1) nounwind
Try to lower memset/memcpy/memmove to vector instructions on ARM where the alignment permits. llvm-svn: 143582 2011-11-03 06:52:45 +08:00			`; RUN: llc -march=arm -mcpu=cortex-a8 < %s \| FileCheck %s`

			`; Trigger multiple NEON stores.`
CriticalAntiDepBreaker is no longer needed for armv7 scheduling. This is being disabled because it is no longer needed for performance. It is only used by postRAscheduler which is also planned for removal, and it is implemented with an out-dated view of register liveness. It consideres aliases instead of register units, assumes valid kill flags, and assumes implicit uses on partial register defs. Kill flags and implicit operands are error prone and impossible to verify. We should gradually eliminate dependence on them in the postRA phases. Targets that still benefit from this should move to the MI scheduler. If that doesn't solve the problem, then we should add a hook to regalloc to optimize reload placement. llvm-svn: 191348 2013-09-25 08:26:16 +08:00			`; CHECK: vst1.64`
			`; CHECK: vst1.64`
Try to lower memset/memcpy/memmove to vector instructions on ARM where the alignment permits. llvm-svn: 143582 2011-11-03 06:52:45 +08:00			`define void @f_0_40(i8* nocapture %c) nounwind optsize {`
			`entry:`
			`call void @llvm.memset.p0i8.i64(i8* %c, i8 0, i64 40, i32 16, i1 false)`
			`ret void`
			`}`

			`declare void @llvm.memset.p0i8.i64(i8* nocapture, i8, i64, i32, i1) nounwind`