summaryrefslogtreecommitdiffstats
path: root/llvm/test
diff options
context:
space:
mode:
authorCharles Davis <cdavis5x@gmail.com>2015-02-27 21:11:16 +0000
committerCharles Davis <cdavis5x@gmail.com>2015-02-27 21:11:16 +0000
commit83687fb9e654c9d0086e7f6b728c26fa0b729e71 (patch)
tree9caf33ad3f62641433067d9728ea3e87ff1333a4 /llvm/test
parentd7b6aa3251a3512025fa8488014eae03ca0c3fd2 (diff)
downloadbcm5719-llvm-83687fb9e654c9d0086e7f6b728c26fa0b729e71.tar.gz
bcm5719-llvm-83687fb9e654c9d0086e7f6b728c26fa0b729e71.zip
Target/X86: Never use the redzone for Win64 ABI functions.
Summary: Until now, we did this (among other things) based on whether or not the target was Windows. This is clearly wrong, not just for Win64 ABI functions on non-Windows, but for System V ABI functions on Windows, too. In this change, we make this decision based on the ABI the calling convention specifies instead. Reviewers: rnk Subscribers: llvm-commits Differential Revision: http://reviews.llvm.org/D7953 llvm-svn: 230793
Diffstat (limited to 'llvm/test')
-rw-r--r--llvm/test/CodeGen/X86/2009-06-03-Win64DisableRedZone.ll3
1 files changed, 2 insertions, 1 deletions
diff --git a/llvm/test/CodeGen/X86/2009-06-03-Win64DisableRedZone.ll b/llvm/test/CodeGen/X86/2009-06-03-Win64DisableRedZone.ll
index 98b1e0ed2f4..8d387136da9 100644
--- a/llvm/test/CodeGen/X86/2009-06-03-Win64DisableRedZone.ll
+++ b/llvm/test/CodeGen/X86/2009-06-03-Win64DisableRedZone.ll
@@ -1,7 +1,8 @@
; RUN: llc -mtriple=x86_64-mingw32 < %s | FileCheck %s
+; RUN: llc -mtriple=x86_64-linux < %s | FileCheck %s
; CHECK-NOT: -{{[1-9][0-9]*}}(%rsp)
-define x86_fp80 @a(i64 %x) nounwind readnone {
+define x86_64_win64cc x86_fp80 @a(i64 %x) nounwind readnone {
entry:
%conv = sitofp i64 %x to x86_fp80 ; <x86_fp80> [#uses=1]
ret x86_fp80 %conv
OpenPOWER on IntegriCloud