mirror of
https://github.com/c64scene-ar/llvm-6502.git
synced 2024-09-03 02:30:00 +00:00
086791eca2
One unusual feature of the z architecture is that the result of a previous load can be reused indefinitely for subsequent loads, even if a cache-coherent store to that location is performed by another CPU. A special serializing instruction must be used if you want to force a load to be reattempted. Since volatile loads are not supposed to be omitted in this way, we should insert a serializing instruction before each such load. The same goes for atomic loads. The patch implements this at the IR->DAG boundary, in a similar way to atomic fences. It is a no-op for targets other than SystemZ. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@196905 91177308-0d34-0410-b5e6-96231b3b80d8
22 lines
576 B
LLVM
22 lines
576 B
LLVM
; Test serialization instructions.
|
|
;
|
|
; RUN: llc < %s -mtriple=s390x-linux-gnu -mcpu=z10 | \
|
|
; RUN: FileCheck %s -check-prefix=CHECK-FULL
|
|
; RUN: llc < %s -mtriple=s390x-linux-gnu -mcpu=z196 | \
|
|
; RUN: FileCheck %s -check-prefix=CHECK-FAST
|
|
|
|
; Check that volatile loads produce a serialisation.
|
|
define i32 @f1(i32 *%src) {
|
|
; CHECK-FULL-LABEL: f1:
|
|
; CHECK-FULL: bcr 15, %r0
|
|
; CHECK-FULL: l %r2, 0(%r2)
|
|
; CHECK-FULL: br %r14
|
|
;
|
|
; CHECK-FAST-LABEL: f1:
|
|
; CHECK-FAST: bcr 14, %r0
|
|
; CHECK-FAST: l %r2, 0(%r2)
|
|
; CHECK-FAST: br %r14
|
|
%val = load volatile i32 *%src
|
|
ret i32 %val
|
|
}
|