1
0
mirror of https://github.com/RPCS3/llvm-mirror.git synced 2024-11-23 19:23:23 +01:00
llvm-mirror/test/CodeGen/X86/pr11985.ll
Craig Topper d094523cbe [X86] Make Feature64Bit useful
We now only add +64bit to the CPU string for "generic" CPU. All other CPU names are assumed to have the feature flag already set if they support 64-bit. I've remove the implies from CMPXCHG8 so that Feature64Bit only comes in via CPUs or user passing -mattr=+64bit.

I've changed the assert to a report_fatal_error so it's not lost in Release builds.

The test updates are to fix things that tripped the new error.

Differential Revision: https://reviews.llvm.org/D51231

llvm-svn: 341022
2018-08-30 06:01:05 +00:00

36 lines
1.3 KiB
LLVM

; RUN: llc < %s -mtriple=x86_64-pc-linux -mcpu=nocona | FileCheck %s --check-prefix=PRESCOTT
; RUN: llc < %s -mtriple=x86_64-pc-linux -mcpu=nehalem | FileCheck %s --check-prefix=NEHALEM
;;; TODO: (1) Some of the loads and stores are certainly unaligned and (2) the first load and first
;;; store overlap with the second load and second store respectively.
;;;
;;; Is either of these sequences ideal?
define float @foo(i8* nocapture %buf, float %a, float %b) nounwind uwtable {
; PRESCOTT-LABEL: foo:
; PRESCOTT: # %bb.0: # %entry
; PRESCOTT-NEXT: movq .Ltmp0+14(%rip), %rax
; PRESCOTT-NEXT: movq %rax, 14(%rdi)
; PRESCOTT-NEXT: movq .Ltmp0+8(%rip), %rax
; PRESCOTT-NEXT: movq %rax, 8(%rdi)
; PRESCOTT-NEXT: movq .Ltmp0(%rip), %rax
; PRESCOTT-NEXT: movq %rax, (%rdi)
;
; NEHALEM-LABEL: foo:
; NEHALEM: # %bb.0: # %entry
; NEHALEM-NEXT: movq .Ltmp0+14(%rip), %rax
; NEHALEM-NEXT: movq %rax, 14(%rdi)
; NEHALEM-NEXT: movups .Ltmp0(%rip), %xmm2
; NEHALEM-NEXT: movups %xmm2, (%rdi)
entry:
tail call void @llvm.memcpy.p0i8.p0i8.i64(i8* %buf, i8* blockaddress(@foo, %out), i64 22, i1 false)
br label %out
out: ; preds = %entry
%add = fadd float %a, %b
ret float %add
}
declare void @llvm.memcpy.p0i8.p0i8.i64(i8* nocapture, i8* nocapture, i64, i1) nounwind