mirror of
https://github.com/c64scene-ar/llvm-6502.git
synced 2024-08-01 17:29:33 +00:00
bbd8c33ee6
out of sync with regular cc. The only difference between the tail call cc and the normal cc was that one parameter register - R9 - was reserved for calling functions through a function pointer. After time the tail call cc has gotten out of sync with the regular cc. We can use R11 which is also caller saved but not used as parameter register for potential function pointers and remove the special tail call cc on x86-64. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@73233 91177308-0d34-0410-b5e6-96231b3b80d8
16 lines
667 B
LLVM
16 lines
667 B
LLVM
; RUN: llvm-as < %s | llc -tailcallopt -march=x86-64 -mattr=+sse2 -mtriple=x86_64-apple-darwin | grep fstpt
|
|
; RUN: llvm-as < %s | llc -tailcallopt -march=x86-64 -mattr=+sse2 -mtriple=x86_64-apple-darwin | grep xmm
|
|
|
|
; Check that x86-64 tail calls support x86_fp80 and v2f32 types. (Tail call
|
|
; calling convention out of sync with standard c calling convention on x86_64)
|
|
; Bug 4278.
|
|
|
|
declare fastcc double @tailcallee(x86_fp80, <2 x float>)
|
|
|
|
define fastcc double @tailcall() {
|
|
entry:
|
|
%tmp = fpext float 1.000000e+00 to x86_fp80
|
|
%tmp2 = tail call fastcc double @tailcallee( x86_fp80 %tmp, <2 x float> <float 1.000000e+00, float 1.000000e+00>)
|
|
ret double %tmp2
|
|
}
|