search for: monochromeindustries

(My apologies for the double e-mail, Eric; I neglected to reply to the list.) >> configure: error: Already configured in /Users/rob/Developer/External/llvm-trunk >> make[1]: *** No targets specified and no makefile found. Stop. >> make: *** [cross-compile-build-tools] Error 1 > > You're going to need multiple configures and multiple build directories to do it that

Hello, I’ve spent the past day or so attempting to get LLVM’s libraries built as a Mac OS X-style universal binary, the first step of which is to get them built for each component architecture (i386, x86_64, ppc, and ppc64). The first two are straightforward as I am working on an x86_64 Mac (running Mac OS X 10.6, which corresponds to Darwin 10), but building ppc binaries has thus far eluded me.

>> The configure script’s output says, near the top: >> >> checking target architecture... x86_64 >> >> So it seems that the Makefile is preferring the configure script’s reckoning to the CFLAGS/CXXFLAGS variables at present. > > configure really doesn't know about it. It's still the target architecture. You'll just be adding more. > > Let

Hello all, The Kaleidoscope tutorial shows how to get a void pointer to the a built function, cast it to the appropriate type, and then call it. There isn’t a tutorial using the LLVM C API that I’ve seen, so I’ve been working with bits and pieces found online, and of course the header files. I haven’t been able to find an equivalent to getPointerToFunction as yet, however. The JIT example I

Hello, A project of mine involves adding a new optimization pass, and it might be relatively convenient for me to contribute additions to the C API to wrap the process of adding an optimization pass. Is there any interest in such additions? Would they be welcomed? Rob -- Rob Rix, Unknown Quantity Monochrome Industries -------------- next part -------------- An HTML attachment was scrubbed...

>> Daniel's comments are also good. > > …success! Looks like I spoke a bit too soon. Everything works as far as the fat binaries are concerned, except that -mmacosx-version-min is set to the host’s OS version, not that of the SDK, causing errors when it tries to link against 10.6’s versions of libraries instead of 10.5’s. This patch appears to solve that; it uses the OS version

Hi Duncan, Thanks for the response! > that's because clang is doing something more complicated than you are: it is > producing a function that conforms to the platform ABI for passing parameters. > The platform ABI specifies in this case that the valued should be returned via > a special in-memory mechanism (thus the "sret" extra function parameter) rather > than in

I’m using the C API (with a few additions in a single cpp file) to write a compiler. In one part of my code, I want to build a function that returns a structure. The LLVM Assembly Language Reference Manual gives this as a possible return value: > ret { i32, i8 } { i32 4, i8 2 } Meanwhile, compiling this C function: > Range make_range(Index location, Index length) { > return (Range){