summaryrefslogtreecommitdiffstats
path: root/llvm/test/CodeGen/SPARC
diff options
context:
space:
mode:
authorRoman Lebedev <lebedev.ri@gmail.com>2019-05-30 16:07:11 +0000
committerRoman Lebedev <lebedev.ri@gmail.com>2019-05-30 16:07:11 +0000
commit019d270e43967558de00ee4b6d624a2225a2fb77 (patch)
tree945cdfd751c4c967f28261d5b3b871334ec439c1 /llvm/test/CodeGen/SPARC
parent0317e46a6322037cef6160dd7216dfe0499aaa4b (diff)
downloadbcm5719-llvm-019d270e43967558de00ee4b6d624a2225a2fb77.tar.gz
bcm5719-llvm-019d270e43967558de00ee4b6d624a2225a2fb77.zip
[DAGCombine] Revert of recommit of "binop-with-const hoisting" patches
I was looking into an endless combine loop the uncommitted follow-up patch was causing, and it appears even these patches can exibit such an endless loop. The root cause is that we try to hoist one binop (add/sub) with constant operand, and if we get two such binops both of which are eligible for this hoisting, we get stuck. Some cases may highlight missing constant-folds. Reverts r361871,r361872,r361873,r361874. llvm-svn: 362109
Diffstat (limited to 'llvm/test/CodeGen/SPARC')
-rw-r--r--llvm/test/CodeGen/SPARC/2013-05-17-CallFrame.ll5
1 files changed, 3 insertions, 2 deletions
diff --git a/llvm/test/CodeGen/SPARC/2013-05-17-CallFrame.ll b/llvm/test/CodeGen/SPARC/2013-05-17-CallFrame.ll
index 274e99b114c..1a97e4e317e 100644
--- a/llvm/test/CodeGen/SPARC/2013-05-17-CallFrame.ll
+++ b/llvm/test/CodeGen/SPARC/2013-05-17-CallFrame.ll
@@ -15,9 +15,10 @@ define void @variable_alloca_with_adj_call_stack(i32 %num) {
; V8-NEXT: .cfi_register 15, 31
; V8-NEXT: add %i0, 7, %i0
; V8-NEXT: and %i0, -8, %i0
+; V8-NEXT: add %i0, 8, %i0
; V8-NEXT: sub %sp, %i0, %i0
-; V8-NEXT: add %i0, -8, %sp
-; V8-NEXT: add %i0, 88, %o0
+; V8-NEXT: add %i0, 96, %o0
+; V8-NEXT: mov %i0, %sp
; V8-NEXT: add %sp, -16, %sp
; V8-NEXT: st %o0, [%sp+104]
; V8-NEXT: st %o0, [%sp+100]
OpenPOWER on IntegriCloud