search for: llvm_lib_dirs

Hello, can anyone help me calling native functions from LLVM-Bytecode functions run in the JIT? I have a program which creates an LLVM execution engine and adds modules and functions to it on the fly. I need to call some native functions of my program from bytecode functions which causes some troubles as it appears not to be documented. My test scenario works like the following: I have

Are you able make calls to well known external functions such as printf? As far as I known, this capability is well tested on x86 / Linux. I am wondering if there is some name mangling issue? Evan On Jun 7, 2007, at 8:38 AM, Jan Rehders wrote: > Hello, > > can anyone help me calling native functions from LLVM-Bytecode > functions run in the JIT? > > I have a program

Using cmake should be the right thing if you'd like to support windows, but it seems that no enough effort on this build system, eg http://llvm.org/bugs/show_bug.cgi?id=12157 three months passed, I'am I bit familiar with cmake, so if there tasks pending for absence of developer, I'd like to join. cmake is not perfect but it's open, but many improvements maybe merged upstream.

Hi, > If I recall correctly, in Linux you get the message: > > PPCJITInfo.cpp:382: failed assertion `ResultPtr >= -(1 << 23) && > ResultPtr < (1 << 23) && "Relocation out of range!"' > > > Right? But on OS X you don't have this messsage? Not exactly. There seem to be two problems. Your patch fixes one of them: in OS X I

On 28 Jun 2012, at 08:58, Jean-Daniel Dupas wrote: > It's a chicken and egg problems. Xcode users don't use cmake because it > generates poor Xcode projects. So what *do* XCode users do (to build llvm/clang)? Do they somehow set up XCode to build using the autoconf build system? Do they build llvm/clang outside of XCode? If the answer to either of the last two questions is

...ct in LLVMConfig.cmake if it is being processed on an installed or uninstalled build and assign LLVM_TOOLS_BINARY_DIR accordingly. This can be done, for instance, comparing the values of CMAKE_CURRENT_LIST_FILE and LLVM_INSTALL_PREFIX, with the necessary adjustments. Ditto for LLVM_INCLUDE_DIRS and LLVM_LIB_DIRS. The other two variables your patch touches (LLVM_INSTALL_PREFIX and CMAKE_MODULE_PATH) does not need such corrections, as the former is precisely the *intended* location for an installed build and the later needs modification only for uninstalled builds, as the comment above the IF hints. Apart...