search for: pdfield

Displaying 4 results from an estimated 4 matches for "pdfield".

Did you mean: p_field
2013 Jan 28
1
[LLVMdev] BitCast or GEP?
I have a little simple inheritance thing going on: %struct.PDFrame = type { i64, i64, i8* } %struct.PDField = type { %struct.PDFrame, i8 } Is there any difference between bitcasting a pointer to the struct.PDField to struct.PDFrame, or using GEP to get a pointer to the "super" struct? I'm not even sure it's possible to bitcast in this situation, but I imagine it should be. -- Rick
2013 Jan 24
2
[LLVMdev] What would cause instructions to NOT make it into the module?
> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Sean Silva > Subject: Re: [LLVMdev] What would cause instructions to NOT make it into the module? > It is a pass that can be run like any other pass. See createVerifierPass(). You can also just call verifyModule() with the appropriate parameters; it's defined in
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