search for: addmachowrit

...ric. LLVMTargetMachine::addPassesToEmitFile explicitly checks whether the derived backend TargetMachine implements one of getMachOWriterInfo or getELFWriterInfo, and returns a corresponding FileModel enum value. llc's main function uses the resulting FileModel value to determine which of the {AddMachOWriter,AddELFWriter} functions to call. This is limiting for a number of reasons: 1. If a given platform (e.g. x86) may support both MachO and ELF, MachO will be selected, as it is checked first. This is bad behaviour, it should be up to the user to decide which object format he wants. 2. Extension of...

...:addPassesToEmitFile explicitly checks whether the > derived backend TargetMachine implements one of getMachOWriterInfo or > getELFWriterInfo, and returns a corresponding FileModel enum value. > > llc's main function uses the resulting FileModel value to determine > which of the {AddMachOWriter,AddELFWriter} functions to call. > > This is limiting for a number of reasons: > 1. If a given platform (e.g. x86) may support both MachO and ELF, > MachO will be selected, as it is checked first. This is bad behaviour, > it should be up to the user to decide which object format he...

...explicitly checks whether the >> derived backend TargetMachine implements one of getMachOWriterInfo or >> getELFWriterInfo, and returns a corresponding FileModel enum value. >> >> llc's main function uses the resulting FileModel value to determine >> which of the {AddMachOWriter,AddELFWriter} functions to call. >> >> This is limiting for a number of reasons: >> 1. If a given platform (e.g. x86) may support both MachO and ELF, >> MachO will be selected, as it is checked first. This is bad behaviour, >> it should be up to the user to decide wh...

...JVM based language (http://openquark.org) to LLVM. A main motivator though is language/library/platform integration on the Mac (Cocoa, Objective-C, autozone). I'm not too interested in a JIT at this point, but rather native code generation. So far I can see a MachOWriter (with an "AddMachOWriter" in FileWriters.h) and it looks like I get to pass an appropriate TargetMachine to this. I'm wondering if this is expected to be sufficient (added to a pass manager) to be able to output a library on the Mac - whether or not it actually works. I only picked LLVM up yesterday, so...

...explicitly checks whether the >> derived backend TargetMachine implements one of getMachOWriterInfo or >> getELFWriterInfo, and returns a corresponding FileModel enum value. >> >> llc's main function uses the resulting FileModel value to determine >> which of the {AddMachOWriter,AddELFWriter} functions to call. >> >> This is limiting for a number of reasons: >> 1. If a given platform (e.g. x86) may support both MachO and ELF, >> MachO will be selected, as it is checked first. This is bad behaviour, >> it should be up to the user to decide wh...

Thanks John. I had passed over ExecutionEngine as it looked like it offered a JIT. Maybe there's more to it than meets the (hasty) eye though. I'm interested in getting a native image. Ultimately, I'd like to do things like emitting Objective-C IMPs and building Objective-C classes around them. However, I'm going one step at a time (there's probably much to learn

I'm a total LLVM n00b, and have just started to work through some of the tutorials with the intention of gathering a clear picture of what LLVM does and doesn't do for a possible project. I'm on the Mac, and would like to have my code dynamically create and load new functions into a process. I believe I can do this, but I'm not sure yet how 'direct' things will be