Displaying 6 results from an estimated 6 matches for "llvm_lib_dir".
Did you mean:
llvm_libs_dir
2007 Jun 07
2
[LLVMdev] How to call native functions from bytecode run in JIT?
...which will call "get5" it will
fail on OS X, too. I have attached the whole .cpp file containing the
complete code. It's adapted from the JIT example in the LLVM source
distribution. I compile it using
g++ -c codegen1.cpp -o codegen1.o -D__STDC_LIMIT_MACROS
g++ -o codegen1 -L${LLVM_LIB_DIR} codegen1.o ${LLVM_LIB_DIR}/
LLVMPowerPC.o -lLLVMSelectionDAG ${LLVM_LIB_DIR}/LLVMInterpreter.o $
{LLVM_LIB_DIR}/LLVMJIT.o -lLLVMCodeGen -lLLVMScalarOpts -
lLLVMTransformUtils -lLLVMipa -lLLVMAnalysis ${LLVM_LIB_DIR}/
LLVMExecutionEngine.o -lLLVMTarget -lLLVMCore -lLLVMSupport -
lLLVMbzip2 -lL...
2007 Jun 10
0
[LLVMdev] How to call native functions from bytecode run in JIT?
...uot; it will
> fail on OS X, too. I have attached the whole .cpp file containing
> the complete code. It's adapted from the JIT example in the LLVM
> source distribution. I compile it using
>
> g++ -c codegen1.cpp -o codegen1.o -D__STDC_LIMIT_MACROS
> g++ -o codegen1 -L${LLVM_LIB_DIR} codegen1.o ${LLVM_LIB_DIR}/
> LLVMPowerPC.o -lLLVMSelectionDAG ${LLVM_LIB_DIR}/LLVMInterpreter.o $
> {LLVM_LIB_DIR}/LLVMJIT.o -lLLVMCodeGen -lLLVMScalarOpts -
> lLLVMTransformUtils -lLLVMipa -lLLVMAnalysis ${LLVM_LIB_DIR}/
> LLVMExecutionEngine.o -lLLVMTarget -lLLVMCore -lLLVMSuppo...
2012 Jun 28
0
[LLVMdev] [cfe-dev] is configure+make dead yet?
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.
2007 Jun 30
1
[LLVMdev] How to call native functions from bytecode run in JIT?
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
2012 Jun 28
3
[LLVMdev] [cfe-dev] is configure+make dead yet?
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
2012 Jun 28
2
[LLVMdev] [cfe-dev] is configure+make dead yet?
...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...