Displaying 4 results from an estimated 4 matches for "mcompletionproc".
Did you mean:
completionproc
2013 Jan 20
2
[LLVMdev] Clang's approach to anonymous struct pointer parameters
For the following code:
struct XBeePacket;
typedef void (*CompletionProc)(XBeePacket* inPacket, void* inParam2);
struct
XBeePacket
{
bool mField1;
CompletionProc mCompletionProc;
};
Why does clang emit this IR?
%struct.XBeePacket = type { i8, {}* }
define void
@MyCompletionProc(%struct.XBeePacket* %inPacket, i8* %inParam2)
nounwind uwtable ssp
{
entry:
...
}
It makes the struct field for the completion proc an an anonymous...
2013 Jan 20
0
[LLVMdev] Clang's approach to anonymous struct pointer parameters
...:57:37 Rick Mann wrote:
> For the following code:
>
> struct XBeePacket;
>
> typedef void (*CompletionProc)(XBeePacket* inPacket, void* inParam2);
>
> struct
> XBeePacket
> {
> bool mField1;
> CompletionProc mCompletionProc;
> };
>
> Why does clang emit this IR?
>
> %struct.XBeePacket = type { i8, {}* }
>
> define void
> @MyCompletionProc(%struct.XBeePacket* %inPacket, i8* %inParam2)
> nounwind uwtable ssp
> {
> entry:
> ...
> }
&g...
2013 Jan 30
0
[LLVMdev] Calling dispatch_async() within call to ExecutionEngine::runFunction()
I have used libdispatch (on FreeBSD) from JIT'd code without any issues, so I think your bug is elsewhere.
David
On 30 Jan 2013, at 07:43, Rick Mann wrote:
> My host app calls runFunction() on my JITed code. It, in turn, calls a C function ("decode()") in the host app that then calls dispatch_async(). The runFunction() call returns as expected, but the block passed to
2013 Jan 30
3
[LLVMdev] Calling dispatch_async() within call to ExecutionEngine::runFunction()
My host app calls runFunction() on my JITed code. It, in turn, calls a C function ("decode()") in the host app that then calls dispatch_async(). The runFunction() call returns as expected, but the block passed to dispatch_async() never gets called. The async block is supposed to call a function pointer callback that was passed in to decode().
Everything is being called on the main