Skip to content

Commit bd3bde8

Browse files
committed
[X86] mfence.ll - add COMMON prefix + replace X32 with X86 prefix
We try to only use X32 for gnux32 triple Noticed while reviewing #106555
1 parent e9de91e commit bd3bde8

File tree

1 file changed

+12
-17
lines changed

1 file changed

+12
-17
lines changed

llvm/test/CodeGen/X86/mfence.ll

Lines changed: 12 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,30 +1,25 @@
11
; NOTE: Assertions have been autogenerated by utils/update_llc_test_checks.py
2-
; RUN: llc < %s -mtriple=i386-unknown-unknown -mattr=+sse2 | FileCheck %s --check-prefix=X32
3-
; RUN: llc < %s -mtriple=x86_64-unknown-unknown -mattr=-sse2 | FileCheck %s --check-prefix=X64
2+
; RUN: llc < %s -mtriple=i386-unknown-unknown -mattr=+sse2 | FileCheck %s --check-prefixes=CHECK,X86
3+
; RUN: llc < %s -mtriple=x86_64-unknown-unknown -mattr=-sse2 | FileCheck %s --check-prefixes=CHECK,X64
44

55
; It doesn't matter if an x86-64 target has specified "no-sse2"; we still can use mfence.
66

77
define void @test() {
8-
; X32-LABEL: test:
9-
; X32: # %bb.0:
10-
; X32-NEXT: mfence
11-
; X32-NEXT: retl
12-
;
13-
; X64-LABEL: test:
14-
; X64: # %bb.0:
15-
; X64-NEXT: mfence
16-
; X64-NEXT: retq
8+
; CHECK-LABEL: test:
9+
; CHECK: # %bb.0:
10+
; CHECK-NEXT: mfence
11+
; CHECK-NEXT: ret{{[l|q]}}
1712
fence seq_cst
1813
ret void
1914
}
2015

2116
define i32 @fence(ptr %ptr) {
22-
; X32-LABEL: fence:
23-
; X32: # %bb.0:
24-
; X32-NEXT: movl {{[0-9]+}}(%esp), %eax
25-
; X32-NEXT: mfence
26-
; X32-NEXT: movl (%eax), %eax
27-
; X32-NEXT: retl
17+
; X86-LABEL: fence:
18+
; X86: # %bb.0:
19+
; X86-NEXT: movl {{[0-9]+}}(%esp), %eax
20+
; X86-NEXT: mfence
21+
; X86-NEXT: movl (%eax), %eax
22+
; X86-NEXT: retl
2823
;
2924
; X64-LABEL: fence:
3025
; X64: # %bb.0:

0 commit comments

Comments
 (0)