search for: callbackname

...tion be registered as callback with the execution engines and the program being compiled by LLVM should be able to make a callback into that function inside lli during its execution. *Design:* 1. The user programs link with a dummy library function called PerformCustomCallback(const char* CallbackName, void *Args). 2. LLVM ExecutionEngines (JIT and MCJIT) will implement this function to perform the multiplexing of the various callbacks registered with them. 3. Whenever the user program calls PerformCustomCallback with appropriate arguments, lli should experience a call to one of th...

...callback into that function > inside lli during its execution. > What are you using lli for that you are running into this problem? -- Sean Silva > > > *Design:* > > 1. The user programs link with a dummy library function called > PerformCustomCallback(const char* CallbackName, void *Args). > > 2. LLVM ExecutionEngines (JIT and MCJIT) will implement this > function to perform the multiplexing of the various callbacks registered > with them. > > 3. Whenever the user program calls PerformCustomCallback with > appropriate arguments, lli shou...

...function be registered as callback with the execution engines and the program being compiled by LLVM should be able to make a callback into that function inside lli during its execution. Design: 1. The user programs link with a dummy library function called PerformCustomCallback(const char* CallbackName, void *Args). 2. LLVM ExecutionEngines (JIT and MCJIT) will implement this function to perform the multiplexing of the various callbacks registered with them. 3. Whenever the user program calls PerformCustomCallback with appropriate arguments, lli should experience a call to one of the...