Displaying 2 results from an estimated 2 matches for "functioncallargumentconversion".
2006 Sep 02
2
[LLVMdev] gfortran calling convention
...acktraces and
inspection in the debugger, I did notice that there is not yet a
calling convention in CallingConv.h for Fortran, and llvm-convert only
tests for CallingConv:C and CSRet, so I suspect that the different CCs
is a problem here.
It looks like I will have to implement a complement to the
FunctionCallArgumentConversion class in llvm-convert.c for the Fortran
CC, but I'm not clear on the role of the CallingConv ID enum. Does a
Fortran CC belong in there, or is that only for the back end?
Thanks,
-mike
--
Michael McCracken
UCSD CSE PhD Candidate
research: http://www.cse.ucsd.edu/~mmccrack/
misc: http://michae...
2006 Sep 02
0
[LLVMdev] gfortran calling convention
...llvm-convert only
> tests for CallingConv:C and CSRet, so I suspect that the different CCs
> is a problem here.
I don't think that that would be necessary, gfortran (IIUC) uses C calling
conventions for easy interop.
> It looks like I will have to implement a complement to the
> FunctionCallArgumentConversion class in llvm-convert.c for the Fortran
> CC, but I'm not clear on the role of the CallingConv ID enum. Does a
> Fortran CC belong in there, or is that only for the back end?
I don't *think* you'll need to do that, the first thing to find out is why
the prototype for the functio...