similar to: [LLVMdev] n00b question: From module/bitcode to Mach-O dylib file directly?

> Aaah. Wasn't quite sure what you were doing here. I'm not positive > what llvm can emit via the writers (there's support for all parts of > the file format), but it could be extended to write one out. I'm just > not quite sure why :) > > -eric Well, ultimately I'm curious about what it would take to port a JVM based language (http://openquark.org) to

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

> > I for one would really like to see object generation become a fully > working feature of the llvm toolchain. Actually, a related thing I've been curious about is the difference between the output of the llvm-gcc-4.2 front end on the Mac and a regular plain vanilla bit code file. The former file can be named a .o and the platform linker now knows how to do LTO while linking

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

> It is simpler. There is not any Mach-O envelope. The platform linker > can directly read Mach-O files as well as llvm bit-code file (using > llvm bit-code file reader). > > > Not sure if/where the exact form of the Mach-O file that carries bit > > code is documented. Thanks for that. Yes, I see what you mean (no Mach-O envelope), yet there seems to be something

> Anyway, I should be able to figure it out from here - thanks again. ...which I did - though I had to ensure I had the target triple set in the module just right: "x86_64-apple-darwin" Originally I tried "i686-apple-darwin9" as this is what gcc reports, and what gets burnt into config.h as: #define LLVM_HOSTTRIPLE "i686-apple-darwin9.6.0" However, it dawned

On 16-Mar-09, at 9:50 PM, Luke Evans wrote: > ...which I did - though I had to ensure I had the target triple set > in the module just right: "x86_64-apple-darwin" D'oh. Spoke too soon (sort of). I have apparently managed to create a bit-code file that will happily be ingested by ld. The dylib that comes out has my symbol in it (according to nm). However, my call to

Hello! I am working with LLVM project to compile for specific processor (xPEC-processor from NetX chip, http://hilscher.com/ ). I have done support of this target successfully! Assembler code can be emitted with debug information. LLVM - great!) But now I am looking for generation of machine code for my target. I have seen, that "llc" has option "-filetype". It has

On Mon, Jul 27, 2009 at 8:25 AM, Rudskyy<tema13tema at yahoo.de> wrote: > But now I am looking for generation of machine code for my target. I have > seen, that “llc” has option "-filetype". > > It has default value "-filetype=asm", but has more values, as > "-filetype=obj" and "-filetype=dynlib". > > “obj” is very interesting, but

On Wed, 12 Apr 2006 22:48:16 -0500 Patrick Meredith <pmeredit at uiuc.edu> wrote: > > On Apr 12, 2006, at 10:23 PM, Simon Burton wrote: > > > > > Is it possible to get llvm to generate native machine code > > without using gcc and friends ? Do I use lli ? > > llc. llc --help lists all the options. it compiles llvm bytecode > files. It seems this

> On Feb 27, 2016, at 4:36 AM, Jun Koi via llvm-dev <llvm-dev at lists.llvm.org> wrote: > The problem is that llvm-mc always compiles "jmp" this as short jump, no matter where the target is. Hence my question. I dont know if there is any way to change this behavior. Looks like a bug to me so far. It isn't. It's just created some assembly which, when assembled, may

On Feb 28, 2016 12:08 AM, "Stephen Checkoway" <s at pahtak.org> wrote: > > > > > On Feb 27, 2016, at 4:36 AM, Jun Koi via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > The problem is that llvm-mc always compiles "jmp" this as short jump, no matter where the target is. Hence my question. I dont know if there is any way to change this

Hi Kev, I'm glad to hear llvm-objdump is getting attention. I'm unclear on how much output specialization one could (or should) do for ELF vs. Mach-O. If you're game, let's compare an example: $ cat labeltest.s .text foo: nop bar: bum: nop jmp bar jmp bum jmp baz nop baz: nop Assembling for x86 and llvm-objdump'ing, i get $ llvm-mc

Hello, While trying to find out why the LDC compiler refuses to generate object code for MSP430 targets (but generates MSP430 assembly or LLVM IR/bitcode), I came across the following apparent inconsistency. This works: $ clang --target=msp430 -c test.c This doesn't work: $ clang --target=msp430 -S -emit-llvm test.c $ llc -filetype=obj test.ll /opt/msp430/bin/llc: target does not support

To the right list this time. On Tue, Oct 18, 2016 at 12:43 PM Eric Christopher <echristo at gmail.com> wrote: > Hi Peter, > > Coming back to his now. > > > IFCC, the previous attempt to teach LLVM to emit jump tables, was removed > for complicating how functions are emitted, in particular requiring a > subtarget-specific instruction emitter available in

Here you go: http://www.cornwarning.com/xfer/jccolor.o (from the jpeg library...) jccolor.o: Mach header magic cputype cpusubtype caps filetype ncmds sizeofcmds flags MH_MAGIC_64 X86_64 ALL 0x00 OBJECT 4 432 SUBSECTIONS_VIA_SYMBOLS Load command 0 cmd LC_SEGMENT_64 cmdsize 312 segname vmaddr 0x0000000000000000 vmsize 0x0000000000000900

Hi ! > Sorry I missed responding to this email sooner. No problem, I was not in a hurry. :) > The approximate approach I had in mind sounds like what you describe, Ok Cool ! > I have been meaning to do this, but won't have time for a couple weeks I suspect. So I will give it a try. :) I was able to quickly hack a JITObjectWriter and I am able to execute simple functions (with

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I mentioned a ghost file. Here is the dump (less than 65M): http://dev.mccme.ru/~raskin/btrfs.dump ghost file is: 885dj1l4788pymp3bk2f3dz52ggcvw4v-empty/garbage-1/mwave.h.tmp-31838-1822528541 It has a name, but stat fails (so no inode, I guess). Also I can create another file with the same name in the directory. I cannot remove the file, or

Chris Lattner wrote: >> The TargetMachine class has a method 'addPassesToEmitMachineCode', that's >> suitable for that, but that method also requires an instance of >> MachineCodeEmitter. > > Actually, you probably want to plug into the addPassesToEmitFile API, when > FileType is set to ObjectFile. X86TargetMachine::addPassesToEmitFile > demonstrates

Hi, I''m glad to announce that I have mostly finished a port of GNU Mach to Xen, so that GNU/Hurd/Mach/Xen now works :) Samuel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel