mirror of
https://github.com/c64scene-ar/llvm-6502.git
synced 2025-10-31 08:16:47 +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
22 lines
724 B
LLVM
22 lines
724 B
LLVM
; RUN: llc < %s -mattr=-vsx -march=ppc32 | grep fcmp | count 1
|
|
|
|
declare i1 @llvm.isunordered.f64(double, double)
|
|
|
|
define i1 @intcoord_cond_next55(double %tmp48.reload) {
|
|
newFuncRoot:
|
|
br label %cond_next55
|
|
|
|
bb72.exitStub: ; preds = %cond_next55
|
|
ret i1 true
|
|
|
|
cond_next62.exitStub: ; preds = %cond_next55
|
|
ret i1 false
|
|
|
|
cond_next55: ; preds = %newFuncRoot
|
|
%tmp57 = fcmp oge double %tmp48.reload, 1.000000e+00 ; <i1> [#uses=1]
|
|
%tmp58 = fcmp uno double %tmp48.reload, 1.000000e+00 ; <i1> [#uses=1]
|
|
%tmp59 = or i1 %tmp57, %tmp58 ; <i1> [#uses=1]
|
|
br i1 %tmp59, label %bb72.exitStub, label %cond_next62.exitStub
|
|
}
|
|
|