maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/test/CodeGen/ARM/movt-movw-global.ll

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

40 lines
1.5 KiB
LLVM
Raw Normal View History

Transfer memory operands to the right instruction. They need to go on the PICLDR as the verifier points out. llvm-svn: 157151
2012-05-20 14:38:42 +08:00
; RUN: llc < %s -verify-machineinstrs -mtriple=armv7-eabi | FileCheck %s -check-prefix=EABI
; RUN: llc < %s -verify-machineinstrs -mtriple=armv7-apple-ios -relocation-model=dynamic-no-pic | FileCheck %s -check-prefix=IOS
; RUN: llc < %s -verify-machineinstrs -mtriple=armv7-apple-ios -relocation-model=pic | FileCheck %s -check-prefix=IOS-PIC
; RUN: llc < %s -verify-machineinstrs -mtriple=armv7-apple-ios -relocation-model=static | FileCheck %s -check-prefix=IOS-STATIC
Materialize global addresses via movt/movw pair, this is always better than doing the same via constpool: 1. Load from constpool costs 3 cycles on A9, movt/movw pair - just 2. 2. Load from constpool might stall up to 300 cycles due to cache miss. 3. Movt/movw does not use load/store unit. 4. Less constpool entries => better compiler performance. This is only enabled on ELF systems, since darwin does not have needed relocations (yet). llvm-svn: 89720
2009-11-24 08:44:37 +08:00
Add iOS test llvm-svn: 132203
2011-05-28 03:04:21 +08:00
@foo = common global i32 0
Materialize global addresses via movt/movw pair, this is always better than doing the same via constpool: 1. Load from constpool costs 3 cycles on A9, movt/movw pair - just 2. 2. Load from constpool might stall up to 300 cycles due to cache miss. 3. Movt/movw does not use load/store unit. 4. Less constpool entries => better compiler performance. This is only enabled on ELF systems, since darwin does not have needed relocations (yet). llvm-svn: 89720
2009-11-24 08:44:37 +08:00
Add iOS test llvm-svn: 132203
2011-05-28 03:04:21 +08:00
define i32* @bar1() nounwind readnone {
Materialize global addresses via movt/movw pair, this is always better than doing the same via constpool: 1. Load from constpool costs 3 cycles on A9, movt/movw pair - just 2. 2. Load from constpool might stall up to 300 cycles due to cache miss. 3. Movt/movw does not use load/store unit. 4. Less constpool entries => better compiler performance. This is only enabled on ELF systems, since darwin does not have needed relocations (yet). llvm-svn: 89720
2009-11-24 08:44:37 +08:00
entry:
Add iOS test llvm-svn: 132203
2011-05-28 03:04:21 +08:00
; EABI: movw r0, :lower16:foo
; EABI-NEXT: movt r0, :upper16:foo
; IOS: movw r0, :lower16:L_foo$non_lazy_ptr
; IOS-NEXT: movt r0, :upper16:L_foo$non_lazy_ptr
; IOS-PIC: movw r0, :lower16:(L_foo$non_lazy_ptr-(LPC0_0+8))
; IOS-PIC-NEXT: movt r0, :upper16:(L_foo$non_lazy_ptr-(LPC0_0+8))
Darwin-ARM: use movw/movt for static relocations llvm-svn: 195759
2013-11-26 20:45:05 +08:00
; IOS-STATIC: movw r0, :lower16:_foo
; IOS-STATIC-NEXT: movt r0, :upper16:_foo
Materialize global addresses via movt/movw pair, this is always better than doing the same via constpool: 1. Load from constpool costs 3 cycles on A9, movt/movw pair - just 2. 2. Load from constpool might stall up to 300 cycles due to cache miss. 3. Movt/movw does not use load/store unit. 4. Less constpool entries => better compiler performance. This is only enabled on ELF systems, since darwin does not have needed relocations (yet). llvm-svn: 89720
2009-11-24 08:44:37 +08:00
ret i32* @foo
}
Add iOS test llvm-svn: 132203
2011-05-28 03:04:21 +08:00
define void @bar2(i32 %baz) nounwind {
Materialize global addresses via movt/movw pair, this is always better than doing the same via constpool: 1. Load from constpool costs 3 cycles on A9, movt/movw pair - just 2. 2. Load from constpool might stall up to 300 cycles due to cache miss. 3. Movt/movw does not use load/store unit. 4. Less constpool entries => better compiler performance. This is only enabled on ELF systems, since darwin does not have needed relocations (yet). llvm-svn: 89720
2009-11-24 08:44:37 +08:00
entry:
Add iOS test llvm-svn: 132203
2011-05-28 03:04:21 +08:00
; EABI: movw r1, :lower16:foo
; EABI-NEXT: movt r1, :upper16:foo
; IOS: movw r1, :lower16:L_foo$non_lazy_ptr
; IOS-NEXT: movt r1, :upper16:L_foo$non_lazy_ptr
; IOS-PIC: movw r1, :lower16:(L_foo$non_lazy_ptr-(LPC1_0+8))
; IOS-PIC-NEXT: movt r1, :upper16:(L_foo$non_lazy_ptr-(LPC1_0+8))
Darwin-ARM: use movw/movt for static relocations llvm-svn: 195759
2013-11-26 20:45:05 +08:00
; IOS-STATIC: movw r1, :lower16:_foo
; IOS-STATIC-NEXT: movt r1, :upper16:_foo
Materialize global addresses via movt/movw pair, this is always better than doing the same via constpool: 1. Load from constpool costs 3 cycles on A9, movt/movw pair - just 2. 2. Load from constpool might stall up to 300 cycles due to cache miss. 3. Movt/movw does not use load/store unit. 4. Less constpool entries => better compiler performance. This is only enabled on ELF systems, since darwin does not have needed relocations (yet). llvm-svn: 89720
2009-11-24 08:44:37 +08:00
store i32 %baz, i32* @foo, align 4
ret void
}