search for: irfortarget

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

2012 May 07
2
[LLVMdev] Running Objective-C in the JIT
...nd also contains its own embedded obj-C classes. My first hurdle in doing this was that when the code tried to call Cocoa classes, the obj-C selectors weren't being recognised by the host process's objc_msgSend function.. After quite a bit of hair-pulling, I copied a trick from the lldb::IRForTarget class, which scans the compiled module and replaces any selector constants with explicit function calls to sel_registerName().. By applying a similar transformation to my own modules, I've now managed to successfully invoke selectors on Cocoa classes. But now I've hit a brick wall trying...
2012 May 08
3
[LLVMdev] Running Objective-C in the JIT
.... > > > > My first hurdle in doing this was that when the code tried to call Cocoa > > classes, the obj-C selectors weren't being recognised by the host > > process's objc_msgSend function.. After quite a bit of hair-pulling, I > > copied a trick from the lldb::IRForTarget class, which scans the compiled > > module and replaces any selector constants with explicit function calls > > to sel_registerName().. By applying a similar transformation to my own > > modules, I've now managed to successfully invoke selectors on Cocoa classes. > > &gt...
2012 May 07
0
[LLVMdev] Running Objective-C in the JIT
...embedded obj-C classes. > > My first hurdle in doing this was that when the code tried to call Cocoa > classes, the obj-C selectors weren't being recognised by the host > process's objc_msgSend function.. After quite a bit of hair-pulling, I > copied a trick from the lldb::IRForTarget class, which scans the compiled > module and replaces any selector constants with explicit function calls > to sel_registerName().. By applying a similar transformation to my own > modules, I've now managed to successfully invoke selectors on Cocoa classes. > > But now I'v...
2012 May 08
0
[LLVMdev] Running Objective-C in the JIT
...>>> My first hurdle in doing this was that when the code tried to call Cocoa >>> classes, the obj-C selectors weren't being recognised by the host >>> process's objc_msgSend function.. After quite a bit of hair-pulling, I >>> copied a trick from the lldb::IRForTarget class, which scans the compiled >>> module and replaces any selector constants with explicit function calls >>> to sel_registerName().. By applying a similar transformation to my own >>> modules, I've now managed to successfully invoke selectors on Cocoa classes. >...