search for: objc_msgsend

...m attempting to JIT-compile some code which uses external OSX obj-C classes (Cocoa, etc), and 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 t...

I'm trying to understand the method dispatch in objc_MsgSend. At some point during compilation, ascii selectors are hashed into integer SEL's. Is this hash somehow guaranteed to be unique? If so, how? If not, how are collisions handled? Is this hashing done during the link phase? Any insights/pointers to the code/documentation related to this hashing w...

...vate.h” void test(A *a) { [a foo]; } → When compiling test.mm, foo is not treated as direct, and IR codegen will generate a call to bjc_msgSend. When compiling impl.mm, foo is direct and is removed from the ObjC metadata. We should emit an error message from the global analysis if there exists an objc_msgSend callsite that targets a direct method. With this global analysis, we can claim the invariant that within the link unit, all callsites for a direct method are converted to direct calls. What information do we need for the global analysis? List of direct methods (class-name selector-name) List of obj...

...s external OSX obj-C > > classes (Cocoa, etc), and 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 >...

...le some code which uses external OSX obj-C > classes (Cocoa, etc), and 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&...

This is certainly an option... but keeping up an LLVM backend for the 360 seems like a bit much work. Using Clang's rewriter requires no real low-level maintenance, just creating and maintaining a C library for support functions emitted by the compiler (e.g. objc_msgSend). It seems to create a backend for LLVM targeting the 360 I wouldn't need to create something that outputs XEX's anyway. My custom backend would effectively create object files that the 360's linker would have to be able to recognize. This would mean not only outputting all the correc...

...bj-C >>> classes (Cocoa, etc), and 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...

...08:48, Kevin Wooten a écrit : > This is certainly an option... but keeping up an LLVM backend for the 360 seems like a bit much work. Using Clang's rewriter requires no real low-level maintenance, just creating and maintaining a C library for support functions emitted by the compiler (e.g. objc_msgSend). > The clang rewriter is not the same than LLVM C backend. AFAIK, clang rewriter don't use llvm at all (as it does not perform codegen). It is just a source to source conversion. I don't know how it work yet, but if it is design to output code for the NeXT Runtime, you may have to twe...

Hi. Does anyone have examples of LLVM assembler to create Objective-C objects and send messages? I'm talking about having an Engine hosted within my Objective-C app, and having LLVM bitcode call back into the app. Thanks! -- Rick

this may be slightly off-topic, as it doesn't pertain directly to the R application, but some of the documentation. when reading R's fullrefman.pdf (available from http://cran.r-project.org/doc/manuals/fullrefman.pdf) in Mac OS X's preview.app (version 4.1, on Mac OS 10.5.x), if i try to do a keyword search within the document, the indexing step freezes about 2/3 the way through the

...pretty central to my software, I'd like to be able to revert to the old code (that GCC 4.2 was producing right) if I need to check for differences between the two, or just if other problems arise... In my case, I absolutely need inline asm, since I'm writing functions that do what objc_msgSend does for Obj-C, but for C++. Methods are binded at the start and then I can have C++ setters/getters, and so on... It's a pretty hard thing to do without asm ;) But right now I managed to get it done with small asm blocks, using constraints and clobbers on each of them. And now that it...

You may find it helpful to reference http://www.ibiblio.org/gferg/ldp/GCC-Inline-Assembly-HOWTO.html. In particular, the information regarding clobbers and constraints. Generally speaking, it's best not to use inline assembly at all. What are you trying to do that you find it necessary? On Mar 16, 2010, at 12:30 AM, Fred / Kettch wrote: > Hi, > > I recently switched to LLVM-GCC

I'm slightly confused here, just to be clear: you're planning to go ObjC -> LLVM (via Clang or whatever) -> C, then use the 360 SDK compiler to build that, right? If that's the case, I think it'd be a better option than to use LLVM to directly generate XEXs, and you won't give the TCR guys fits (I checked the BAS TCRs, none of them say you can't do that, but the

On Wed, Oct 19, 2011 at 8:20 PM, Shea Levy <shea at shealevy.com> wrote: > Hello, > > I'd like write a program that performs static analysis of code at the > LLVM assembly/bitcode level, and to do so I plan on extensively > referencing the language reference. As I hope to eventually use this > tool as part of a security analysis of untrusted code, I need to be >

Hi, I recently switched to LLVM-GCC 4.2 on OS X, to go around a bug caused by gcc with optimized code. Unfortunately, I ran into another weird problem on LLVM-GCC. In my code, there's a file with a bunch of inline assembly blocks, that worked fine with GCC 4.2. Now, when compiling with LLVM-GCC 4.2, weird things happen. Here's an example: (the blocks are larger than that, but a single

Hello, I'd like write a program that performs static analysis of code at the LLVM assembly/bitcode level, and to do so I plan on extensively referencing the language reference. As I hope to eventually use this tool as part of a security analysis of untrusted code, I need to be rather strict in my interpretation of the document. As such, I have some questions about how the implementers

We are looking at using Objective-C/C++ in a new game engine.  Objective C's duality of being both very dynamic and very "C" gives us exactly what we need to make the SDK and engineering of games simpler. This means that we will need a way to compile it on all platforms our games will target.  Currently the major platforms we are concerned with include... PC, Mac, XBox 360, PS3,

...dingWithExceptionHandler:] 1 CGSDisableUpdate 1 CGSDisableUpdateForConnections 1 _CGSDisableUpdateForConnections 1 mach_msg 1 mach_msg_trap 1 mach_msg_trap 1 objc_msgSend 1 objc_msgSend 2 objc_msgSend 2 objc_msgSend 1635 Thread_2903 1635 thread_start 1635 _pthread_start 1635 fe_fragment_thread 1635 pthread_cond_wait$UNIX2003 1635 __semwait_signal 163...