llvm-mirror/test/CodeGen/Thumb/barrier.ll

; RUN: llc < %s -mtriple=thumbv6-apple-darwin  | FileCheck %s -check-prefix=V6
; RUN: llc < %s -mtriple=thumbv7-apple-darwin -mattr=-db | FileCheck %s -check-prefix=V6
; RUN: llc < %s -march=thumb -mcpu=cortex-m0   | FileCheck %s -check-prefix=V6M

define void @t1() {
; V6: t1:
; V6: blx {{_*}}sync_synchronize

; V6M: t1:
; V6M: dmb ish
  fence seq_cst
  ret void
}
Fix test and re-enable it. llvm-svn: 110829 2010-08-11 19:25:51 +02:00			`; RUN: llc < %s -mtriple=thumbv6-apple-darwin \| FileCheck %s -check-prefix=V6`
Do not use MEMBARRIER_MCR for any Thumb code. It is only supported for ARM code. Normally Thumb2 code would use DMB instead, but depending on how the compiler is invoked (e.g., -mattr=-db) that might be disabled. This prevents a "cannot select MEMBARRIER_MCR" error in that situation. Radar 8644195 llvm-svn: 118642 2010-11-09 23:50:44 +01:00			`; RUN: llc < %s -mtriple=thumbv7-apple-darwin -mattr=-db \| FileCheck %s -check-prefix=V6`
Change some ARM subtarget features to be single bit yes/no in order to sink them down to MC layer. Also fix tests. llvm-svn: 134590 2011-07-07 05:55:05 +02:00			`; RUN: llc < %s -march=thumb -mcpu=cortex-m0 \| FileCheck %s -check-prefix=V6M`
- Add subtarget feature -mattr=+db which determine whether an ARM cpu has the memory and synchronization barrier dmb and dsb instructions. - Change instruction names to something more sensible (matching name of actual instructions). - Added tests for memory barrier codegen. llvm-svn: 110785 2010-08-11 08:22:01 +02:00
			`define void @t1() {`
Add Cortex-M0 support. It's a ARMv6m device (no ARM mode) with some 32-bit instructions: dmb, dsb, isb, msr, and mrs. llvm-svn: 110786 2010-08-11 08:30:38 +02:00			`; V6: t1:`
Fix test and re-enable it. llvm-svn: 110829 2010-08-11 19:25:51 +02:00			`; V6: blx {{_*}}sync_synchronize`
Add Cortex-M0 support. It's a ARMv6m device (no ARM mode) with some 32-bit instructions: dmb, dsb, isb, msr, and mrs. llvm-svn: 110786 2010-08-11 08:30:38 +02:00
Add ARM Archv6M and let it implies FeatureDB (having dmb, etc.) llvm-svn: 110795 2010-08-11 08:51:54 +02:00			`; V6M: t1:`
Overhaul memory barriers in the ARM backend. Radar 8601999. There were a number of issues to fix up here: * The "device" argument of the llvm.memory.barrier intrinsic should be used to distinguish the "Full System" domain from the "Inner Shareable" domain. It has nothing to do with using DMB vs. DSB instructions. * The compiler should never need to emit DSB instructions. Remove the ARMISD::SYNCBARRIER node and also remove the instruction patterns for DSB. * Merge the separate DMB/DSB instructions for options only used for the disassembler with the default DMB/DSB instructions. Add the default "full system" option ARM_MB::SY to the ARM_MB::MemBOpt enum. * Add a separate ARMISD::MEMBARRIER_MCR node for subtargets that implement a data memory barrier using the MCR instruction. * Fix up encodings for these instructions (except MCR). I also updated the tests and added a few new ones to check for DMB options that were not currently being exercised. llvm-svn: 117756 2010-10-30 02:54:37 +02:00			`; V6M: dmb ish`
Convert more tests to new atomic instructions. llvm-svn: 140567 2011-09-26 23:36:10 +02:00			`fence seq_cst`
- Add subtarget feature -mattr=+db which determine whether an ARM cpu has the memory and synchronization barrier dmb and dsb instructions. - Change instruction names to something more sensible (matching name of actual instructions). - Added tests for memory barrier codegen. llvm-svn: 110785 2010-08-11 08:22:01 +02:00			`ret void`
			`}`