search for: objc4

On Tue, Feb 13, 2018 at 12:18 PM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > On 12 Feb 2018, at 22:31, Stanislav Pankevich via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> Specifically I explored the latest objc4-723 >> from Apple Open Source and it looks like all of the APIs that allow >> the registration of Objective-C classes, selectors, etc. are all very >> private. > > The Objective-C runtime provides public APIs for doing all of this. They’re even documented. They are also mo...

On 12 Feb 2018, at 22:31, Stanislav Pankevich via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Specifically I explored the latest objc4-723 > from Apple Open Source and it looks like all of the APIs that allow > the registration of Objective-C classes, selectors, etc. are all very > private. The Objective-C runtime provides public APIs for doing all of this. They’re even documented. They are also more or less standard a...

...l.com> wrote: > > On Tue, Feb 13, 2018 at 12:18 PM, David Chisnall > <David.Chisnall at cl.cam.ac.uk> wrote: >> On 12 Feb 2018, at 22:31, Stanislav Pankevich via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>> >>> Specifically I explored the latest objc4-723 >>> from Apple Open Source and it looks like all of the APIs that allow >>> the registration of Objective-C classes, selectors, etc. are all very >>> private. >> >> The Objective-C runtime provides public APIs for doing all of this. They’re even document...

...t; On Tue, Feb 13, 2018 at 12:18 PM, David Chisnall > > <David.Chisnall at cl.cam.ac.uk> wrote: > >> On 12 Feb 2018, at 22:31, Stanislav Pankevich via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >>> > >>> Specifically I explored the latest objc4-723 > >>> from Apple Open Source and it looks like all of the APIs that allow > >>> the registration of Objective-C classes, selectors, etc. are all very > >>> private. > >> > >> The Objective-C runtime provides public APIs for doing all of this...

...gt; You can try to load them manually by using the runtime functions (see https://developer.apple.com/library/mac/#documentation/Cocoa/Reference/ObjCRuntimeRef/Reference/reference.html ) and if it's not enough, you may have to download the runtime source code (http://opensource.apple.com/source/objc4/objc4-493.11/) to see what it does when a new module is loaded. > > > -- Jean-Daniel > > > >

...2:18 PM, David Chisnall >> > <David.Chisnall at cl.cam.ac.uk> wrote: >> >> On 12 Feb 2018, at 22:31, Stanislav Pankevich via llvm-dev >> >> <llvm-dev at lists.llvm.org> wrote: >> >>> >> >>> Specifically I explored the latest objc4-723 >> >>> from Apple Open Source and it looks like all of the APIs that allow >> >>> the registration of Objective-C classes, selectors, etc. are all very >> >>> private. >> >> >> >> The Objective-C runtime provides public APIs f...

...gt; >> > <David.Chisnall at cl.cam.ac.uk> wrote: > >> >> On 12 Feb 2018, at 22:31, Stanislav Pankevich via llvm-dev > >> >> <llvm-dev at lists.llvm.org> wrote: > >> >>> > >> >>> Specifically I explored the latest objc4-723 > >> >>> from Apple Open Source and it looks like all of the APIs that allow > >> >>> the registration of Objective-C classes, selectors, etc. are all > very > >> >>> private. > >> >> > >> >> The Objective-C...

...ed. You can try to load them manually by using the runtime functions (see https://developer.apple.com/library/mac/#documentation/Cocoa/Reference/ObjCRuntimeRef/Reference/reference.html ) and if it's not enough, you may have to download the runtime source code (http://opensource.apple.com/source/objc4/objc4-493.11/) to see what it does when a new module is loaded. -- Jean-Daniel

Hello, I've been trying to get some OSX code to execute within the JIT, and it's been causing me some major headaches! I'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

...gt; You can try to load them manually by using the runtime functions (see https://developer.apple.com/library/mac/#documentation/Cocoa/Reference/ObjCRuntimeRef/Reference/reference.html ) and if it's not enough, you may have to download the runtime source code (http://opensource.apple.com/source/objc4/objc4-493.11/) to see what it does when a new module is loaded. >> >> >> -- Jean-Daniel >> >> >> >> -- Jean-Daniel

...happy to provide pointers and code review. Has any progress been made on this issue since 1 year ago? Lang, I have spent some time trying to follow your hints along the lines quoted above and found that it is indeed a non-trivial effort to implement all of this. Specifically I explored the latest objc4-723 from Apple Open Source and it looks like all of the APIs that allow the registration of Objective-C classes, selectors, etc. are all very private. One year ago you said you could help anyone interested in working on this. Let me check here again as a volunteer (if this work can ever be accompl...

Hi, sorry, if I post to the unrelated list. I wish to use code::blocks with the llvm compilers on Windows to use Objective-C 2.0. There are several runtimes with differences in API, how do clang-llvm, llvm-gcc know the type of runtime? I wish to use Apple objc4, is it possible? -- best regards Ariel -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100728/432259b1/attachment.html>

Hi, sorry, if I post to the unrelated list. I wish to use code::blocks with the llvm compilers on Windows to use Objective-C 2.0. There are several runtimes with differences in API, how do clang-llvm, llvm-gcc know the type of runtime? I wish to use Apple objc4, is it possible? -- best regards Ariel -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100728/5cbed1b2/attachment.html>

Hi Kevin I am just pointing out that is a good place to look at how metadata is parsed and it supports parsing metadata from pre-linked object file which is important to JIT. My code pretty much replicate most of the functions in MachODump in C++ and hope it can much more reusable than the c parser. The biggest missing part is the resilience to bad metadata due to the fact we currently don't