search for: grahamwakefield

>> 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, The JIT engine currently uses a single memory block for all functions that you JIT-compile (and global variables, constants, etc..). Still, you can easily create and delete machine code. You can use the following functions: engine->freeMachineCodeForFunction(function); // clean the JITed code function->eraseFromParent(); // clean a function's IR About the lifetime of the classes,

Hi, I apologize in advance if this is not the correct place to ask these questions, but I would be very grateful for redirection to the appropriate list/docs if so. I've just started with LLVM in the last week or so, and have worked my way through the Kaleidoscope tutorial, the IR docs & programmers manual, plus a few of the examples; everything makes sense. But there's one

Quick related Q: Does the global lock of the JIT during code generation prevent concurrent execution of already JIT-ted code? Thanks. On Jan 12, 2009, at 9:34 AM, Gordon Henriksen wrote: > On Jan 12, 2009, at 11:10, Edgar Geisler wrote: > >> my goal is to create a service with multiple threads, each of them >> generating IR code and JIT'ing/executing it in their threads

Sorry if this is a newb q... I'm developing an application on a 10.5 machine but want to target the 10.4 SDK. Is there a magic incantation for the llvm configure script to set the sysroot path, equivalent to e.g. --with-sysroot "/Developer/SDKs/MacOSX10.4u.sdk"? Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL:

I'd love to read this article, but I can't justify paying to register. Will it become a 'freely available' article at any point soon? Thanks On Jan 25, 2009, at 7:16 AM, Jon Harrop wrote: > > Following on from the success of our previous OCaml Journal articles > covering > LLVM, we have begun a series dedicated to the design and > implementation of >

Thanks, that helps. I saw the possibility to redefine function bodies in the Kaleidoscope tutorial. What's not so clear to me yet, is how to support multiple Modules, but it's getting clearer now. Can I run a potential case past you just to be sure that it is/isn't possible? I'd like to support users dynamically adding and using functions (plus structs, globals etc) to a

Hi, For the record, adding UNIVERSAL_SDK_PATH=/Developer/SDKs/MacOSX10.4u.sdk/ was insufficient to restrict the .a/.o files to link against the 10.4 sdk, but env MACOSX_DEPLOYMENT_TARGET=10.4 make did the trick. Thanks! On Jan 14, 2009, at 1:29 PM, Jean-Daniel Dupas wrote: > > Le 14 janv. 09 à 21:48, Chris Lattner a écrit : > >> >> On Jan 14, 2009, at 12:44 PM,

Hi, Was this ever resolved? I'm curious, I'm also in a situation where there may be many (very many) JITted functions over the history of an application (which may be running for many days) Thanks On Mar 20, 2009, at 7:34 AM, George Giorgidze wrote: > Hi, > > In my application I am JITing thousands of functions, though I am > doing it sequantially and running only

Hi, I'm having a hard time linking the LLVM/clang libraries in Xcode. I've been fighting this for a couple of days now, and decided to make a fresh checkout and a super-simple demo project to try and isolate the problem, but even so I'm getting undefined symbol errors in the linker for the static libraries LLVM is producing. This is really baffling, so probably I'm