[prev in list] [next in list] [prev in thread] [next in thread] 

List:       llvm-bugs
Subject:    [LLVMbugs] [Bug 4278] New: X86-64 -tailcallopt calling convention
From:       bugzilla-daemon () cs ! uiuc ! edu
Date:       2009-05-28 9:32:39
Message-ID: bug-4278-206 () http ! llvm ! org/bugs/
[Download RAW message or body]

http://llvm.org/bugs/show_bug.cgi?id=4278

           Summary: X86-64 -tailcallopt calling convention specification
                    seems out-of-sync with regular cc
           Product: new-bugs
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: new bugs
        AssignedTo: unassignedbugs@nondot.org
        ReportedBy: fvbommel@wxs.nl
                CC: llvmbugs@cs.uiuc.edu


In CC_X86_64_TailCall (X86CallingConv.td), there are several differences from
CC_X86_64_C that are not explained (AFAICT) by the need to support tail calls.
* It doesn't support fp80 arguments (causing a "Formal argument #0 has
unhandled type f80" abort).
* v2f32 doesn't seem to be handled either.
* The code that puts MMX vectors in XMM registers on Darwin doesn't check
CCIfSubtarget<"hasSSE2()"> like it does for regular calls.

Also, the comment for the integer registers is a copy-paste-o; there are only 5
of them for tail calls, not 6.


-- 
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
_______________________________________________
LLVMbugs mailing list
LLVMbugs@cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvmbugs
[prev in list] [next in list] [prev in thread] [next in thread]