similar to: [LLVMdev] LLVM Objective-C backend

Its been talked about from time to time. There really isn't anything stopping us from supporting it other than someone putting the time in to modify llvm-gcc to support C and possibly implementing the required runtime libraries for ObjC. Patches welcome! :) Reid. On Wed, 2004-12-08 at 23:01, Sébastien Pierre wrote: > Hello there, > > LLVM has C and C++ backends, so I was wondering

>> 3. Is LLVM able to support advanced runtime features as continuations, >> garbage collection and resuming exception handling. Would there be >> anything in LLVM that would prevent these sorts of features? Is there >> anything in the LLVM runtime that is assumed (dynamic typing, etc). Or >> is LLVM as it's title sugests: Low-Level, so it won't get in your

Le 17 janv. 05, à 00:38, Vikram Adve a écrit : > I think the code for closures (and therefore any first-class > functions) requires excessive use of void pointers and casts. And is there any chance that closure implementation could be made easier ? If LLVM is to be used as a platform for new computer languages, tis would be important. I think that closures would be on the top of the

PLEASE HELP I actually want to do the following: a[j] = (1/(j!))*Π (i-1-d), j = 500, Π means product i = 1 to j   Yet, j! will stop at 170 and Π (i-1-d) at 172; so, a[j] will not exceed 170. I would like to have at least 200 a[j].   WHAT SHOULD I DO?   PLEASE SEE MY CODE FOR DETAIL!! #################################################### R CODE:

Dear useRs, by a circular diagram representation I mean what you will get by entering this at your R promt: pie(1:5) Nice to have R as a lingua franca :-) The folowing quote is from page 360 in this very interesting paper: @article{SpenceI2005, title = {No Humble Pie: The Origins and Usage of a Statistical Chart}, author = {Spence, I.}, journal = {Journal of Educational and

> Dear useRs, > > by a circular diagram representation I mean what you will get by entering > this at your R promt: > > pie(1:5) > > Nice to have R as a lingua franca :-) > > The folowing quote is from page 360 in this very interesting paper: > > @article{SpenceI2005, > title = {No Humble Pie: The Origins and Usage of a Statistical Chart}, >

> So no JIT for i386? I didn't realise i386 still used ObjC 1 - all my experiments were on arm64. i386 support for ObjC would be nice to have, but it's not a blocker for adding ObjC 2 support. - Lang. On Thu, Oct 20, 2016 at 11:57 AM, Steven Wu <stevenwu at apple.com> wrote: > > > > On Oct 19, 2016, at 11:28 AM, Stanislav Pankevich <s.pankevich at

Hi, I just spent two rainy days writing and fine-tuning a post-installation script for CentOS 7 and KDE. https://github.com/kikinovak/centos-7-desktop-kde I've just tested it on three different machines here, and it works quite nicely. Feel free to give it a spin and make some suggestions. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730

Hi Stanislav Thanks for checking on this. If you want a quick hack, you can try to read the code in tools/llvm-objdump/MachODump.cpp. There are some c code in there to parse metadata. My code is something I put up for my own purpose for debugging/parsing objc metadata. The interface is a bit rough to use but the biggest problem is testing. I have my own binary living out of tree to test the

Hi Lang, Steven, At this point it seems that the best next step is for Steven to share his code, right? Or is there some other work that can be done in parallel? Lang? Steven? Here’s small note about my interest here: Alex Denisov and I are working on a tool for mutation testing https://github.com/AlexDenisov/mutang <https://github.com/AlexDenisov/mutang>. Alex has made fascinating

Hi Stanislav, Sorry -- I am not much help here. I would like to get ObjC runtime support for the JIT, but have not had time to look in to it closely. When I last tested the idea (a couple of years ago now) we used selector registration and objc_readClassPair to get basic test cases working as you have, but ran into (possibly similar) failures on non-trivial test cases. I think the interpretation

Hi all, I was just made aware of this: <http://www.codeigniter.com> I wonder where the inspiration comes from? Lots of very similar concepts there ;) I''ve only watched the intro movie so far, but very interesting. jt

Hi again, I had tried to follow David's suggestion to take a step back and look into codegen instead of hacking on RuntimeDyld but then I quickly realized that I don't understand what exactly needs to be done to fully register Objective-C runtime. I decided to iterate on JIT code again and somehow I found that I can hook into SectionMemory by subclassing it and working with its

Hi David, Stanislav, Sorry for the delayed reply. Short version: There hasn't been any progress on this just yet, as I have been busy with an overhaul of the underlying ORC APIs. 1) Hack up something in RuntimeDyldMachO to handle the data structures > currently generated by clang. This is fragile, because the interface > between the compiler and the runtime is not documented, and is

Kevin, On Thu, May 27, 2010 at 11:49 AM, Kevin Wooten <kdubb at me.com> wrote: > To ease our development process, actually hide it completely, we are planning on leveraging the open nature of Clang and LLVM to create a driver for these platforms that first rewrites ObjC to C and then calls the platform's C compiler passing through all command line options. This way the ObjC stage

Hi there, I'm trying to run trivial Objective-C code that uses the Foundation framework under MacOS X in lli. It seems that the code will compile and run using llc, however fails to work in lli. SimpleFoundation.m: ---- #import <Foundation/Foundation.h> int main (int argc, const char * argv[]) { NSAutoreleasePool * pool = [[NSAutoreleasePool alloc] init]; // insert code

Yep... I have been a 360 developer since the days when it was a actual Macintosh G5. I went to all the early tech. seminars and learned way more about that wacky processor and MS's seemingly crazy ABI choices than I care to (I know, I know, they had their reasons for them). Knowing this is why I quickly turned toward rewriting objc instead of attempting to implement a backend. I have also

Hi Stanislav, Lang I have a version of objc metadata parser based on LLVM which can handle objc2 metadata from MachO object and bitcode (bitcode version is even swift compatible). I don't know if there is enough interest for me to upstream it. It probably requires some work to clean up the interface and complete it by adding objc1 support and other object format support. Steven > On Oct

Just to be clear, nothing in the MS TCRs require that you use a certain compiler - it does, however, require that you link with the 360-specific C runtime libraries. That being said, I still believe that direct binary generation is not a feasible option, and the ObjC => C route is preferred. Kevin, hate to be asking this but do you have access to the XDK or are you just "aiming" for

Kevin, there're some unwritten rules on the 360 that seem to interfere with code generation - pointer load-stores seem to require zeroing the most significant 32 bits, for example - that was one issue that I ran into a while ago while fooling around with code generation on the 360 (and don't blame me if I'm slightly off the mark, it was quite a while ago). I didn't seem to find it