similar to: [LLVMdev] RFC: [Proposal] Module-Level Attributes

On Oct 28, 2010, at 5:46 PM, Bill Wendling wrote: > > Comments? Hi Bill, This is a broad solution to what sounds like a specific problem. Are there any other uses for module-level attributes anticipated? Do you anticipate defining what ImageInfo, CorrectedSynthesize, GCOnly, etc. mean in LangRef.html, or are they just going to be left as "The is for ObjC." ? Thanks, Dan

Hi Sandeep, ObjC is the first place that I will use it, of course (we need it to fix LTO). Other uses will come along later. (I don't know enough about the float ABI issues to say whether they should be done via module flags or not.) The OpenCL people have a need for named metadata for their stuff. I would hope that module flags would be a good fit for that, but that remains to be seen. But

Could you expand on likely uses other than ObjC? For example, should float ABI (soft/softfp/hard) be conveyed via this mechanism? deep On Wed, Jan 18, 2012 at 9:36 PM, Bill Wendling <wendling at apple.com> wrote: > Hello, > > This is a proposal for implementing "module flags". Please take a look at this and give any feedback you may have. > > Thanks! > -bw >

Hi Bill, > This is a proposal for implementing "module flags". Please take a look at this and give any feedback you may have. what does this give you that you can't get with the existing scheme of using global variables in a special section? Ciao, Duncan. > > Thanks! > -bw > > Module Flags Metadata > > Information about the module

Hello, This is a proposal for implementing "module flags". Please take a look at this and give any feedback you may have. Thanks! -bw Module Flags Metadata Information about the module as a whole is difficult to convey to LLVM's subsystems. The LLVM IR isn't sufficient to transmit this information. One should instead use the llvm.module.flags named

> LTO would see that the module attributes are incompatible and will reject > trying > to link the two modules. > Comments? Just questions since I am not familiar with objc: *) Is the native linker able to handle this if you don't use LTO? *) -fobjc-gc/-fno-objc-gc have any other impact on functions or data structures? Could you use these to detect the problem? I am just a bit

Hi Bill, For the GNU runtimes, this metadata is stored in the module structure in each compilation unit, and uses a different set of flags. Do you have any plans for this to be generic, or is it intended just for Darwin? David On 19 Jan 2012, at 23:33, Bill Wendling wrote: > Hi Sandeep, > > ObjC is the first place that I will use it, of course (we need it to fix LTO). Other uses

Hi, while generating the PDF file , i am getting following error.. please help for me. RuntimeError (JPEG marker not found!): C:/Ruby/lib/ruby/gems/1.8/gems/pdf-writer-1.1.8/lib/pdf/writer/ graphics/imageinfo.rb:176:in ` measure_JPEG'' C:/Ruby/lib/ruby/gems/1.8/gems/pdf-writer-1.1.8/lib/pdf/writer/ graphics/imageinfo.rb:174:in ` loop''

Hello list, I'm wondering about the feasibility of collapsing the following two globals within llvm-link: @"OBJC_CLASSLIST_REFERENCES_$_2" = private global %struct.objc_class* bitcast (%struct._class_t* @"OBJC_CLASS_$_NSString" to %struct.objc_class*), section "__DATA, __objc_classrefs, regular, no_dead_strip", align 4 @"OBJC_CLASSLIST_REFERENCES_$_8"

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

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

> 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 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 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

On Thu, 19 Jul 2007, Andy Kitchen wrote: > 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. Nice! this is a great project, unfortunately, there are some issues here :) I'm CC'ing Marcel, as he has some experience with

Hi, What would be an estimate for the amount of work required to implement this? Where would I get started if I were to implement it? My goal is to run Objective-C programs in the interpreter so I can provide an application-sandbox by disallowing the invocation of certain C-functions and also by disallowing the invocation of certain Objective-C methods. Thanks, Eric On Oct 19, 2009,

On 6 February 2014 19:21, Richard Smith <richard at metafoo.co.uk> wrote: > > if (nounwind) > can't unwind > can't unwind == unwind table + no EH directives + no EH table if (uwtable || (!nounwind && need uwtable to unwind)) > unwind table > "need unwind table to unwind" is probably true in almost all cases. At least in all where

Hello, Is it possible to execute Objective-C code using LLVM JIT? The original point for my research is this topic on StackOverflow: All selectors unrecognised when invoking Objective-C methods using the LLVM ExecutionEngine http://stackoverflow.com/questions/10375324/all-selectors-unrecognised-when-invoking-objective-c-methods-using-the-llvm-exec

Building with --enable-llvm failed latter on when compiling libojc: configure:5099: checking for exception model to use configure:5131: /home/rafael/dev/gcc/build/gcc/xgcc -B/home/rafael/dev/gcc/build/gcc/ -B/i686-pc-linux-gnu/bin/ -B/i686-pc-linux-gnu/lib/ -isystem /i686-pc-linux-gnu/include -isystem /i686-pc-linux-gnu/sys-include -c -xobjecti ve-c -fgnu-runtime -fobjc-exceptions -S conftest.c

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