mirror of
https://github.com/c64scene-ar/llvm-6502.git
synced 2024-12-26 05:32:25 +00:00
551a3d7b56
We recently discovered an issue that reinforces what a good idea it is to always specify -mcpu in our code generation tests, particularly for -mattr=+vsx. This patch ensures that all tests that specify -mattr=+vsx also specify -mcpu=pwr7 or -mcpu=pwr8, as appropriate. Some of the uses of -mattr=+vsx added recently don't make much sense (when specified for -mtriple=powerpc-apple-darwin8 or -march=ppc32, for example). For cases like this I've just removed the extra VSX test commands; there's enough coverage without them. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@220173 91177308-0d34-0410-b5e6-96231b3b80d8
27 lines
918 B
LLVM
27 lines
918 B
LLVM
; fcfid and fctid should be generated when the 64bit feature is enabled, but not
|
|
; otherwise.
|
|
|
|
; RUN: llc < %s -mattr=-vsx -march=ppc32 -mattr=+64bit | \
|
|
; RUN: grep fcfid
|
|
; RUN: llc < %s -mattr=-vsx -march=ppc32 -mattr=+64bit | \
|
|
; RUN: grep fctidz
|
|
; RUN: llc < %s -mattr=-vsx -march=ppc32 -mcpu=g5 | \
|
|
; RUN: grep fcfid
|
|
; RUN: llc < %s -mattr=-vsx -march=ppc32 -mcpu=g5 | \
|
|
; RUN: grep fctidz
|
|
; RUN: llc < %s -mattr=-vsx -march=ppc32 -mattr=-64bit | \
|
|
; RUN: not grep fcfid
|
|
; RUN: llc < %s -mattr=-vsx -march=ppc32 -mattr=-64bit | \
|
|
; RUN: not grep fctidz
|
|
; RUN: llc < %s -mattr=-vsx -march=ppc32 -mcpu=g4 | \
|
|
; RUN: not grep fcfid
|
|
; RUN: llc < %s -mattr=-vsx -march=ppc32 -mcpu=g4 | \
|
|
; RUN: not grep fctidz
|
|
|
|
define double @X(double %Y) {
|
|
%A = fptosi double %Y to i64 ; <i64> [#uses=1]
|
|
%B = sitofp i64 %A to double ; <double> [#uses=1]
|
|
ret double %B
|
|
}
|
|
|