Displaying 2 results from an estimated 2 matches for "call_native".
2011 Aug 04
2
[LLVMdev] LLVM backend: Treat some function calls specially
...CALL $offsetInByteCode
This works fine so far using the standard machinery of LLVM. But some
functions are not implemented in byte code, but delegated to native
implementations within the VM. Calls to these functions use a non-standard
calling convention and should be lowered to another opcode:
CALL_NATIVE $functionIndex
where $functionIndex is a magic byte telling the VM which native function
should be called. As the set of native functions and function indices will
be extended over time, it should not be hardcoded into the backend but
given as input at compile time.
I have some vague ideas on how...
2011 Aug 04
0
[LLVMdev] LLVM backend: Treat some function calls specially
Jonas,
Why not lower everything to a single call during instruction selection, and then write a machine function pass that translates the normal CALL's into CALL_NATIVE?
Micah
> -----Original Message-----
> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu]
> On Behalf Of Jonas Gefele
> Sent: Thursday, August 04, 2011 9:56 AM
> To: llvmdev at cs.uiuc.edu
> Subject: [LLVMdev] LLVM backend: Treat some function calls spec...