similar to: [LLVMdev] LLVM build failures

Hello EveryOne, I am building customized tools for ARM using a crosscomplier. I am currently building a tool similar to lli but it only jits code. I enabled jit when I was configuring LLVM. On linking my code with help from llvm-config to the libraries I get this error: Can't exec "which": No such file or directory at llvm2/bin/llvm-config line 69. Use of uninitialized value in

Based on cmake/modules/LLVMLibDeps.cmake, I produced a graphviz dot file and then manually removed components and edges until the graph was small enough to be presentable. I don't know if I can actually use LLVM due to its humongousness, but I hope the graph will be helpful to others attempting to comprehend LLVM. PNG attached; dot file follows. digraph G { ipo

With the TableGen problem circumvented the build proceeds quite well up until: llvm[2]: Linking Debug executable llc /home/neale/LLVM/llvm/tools/llc/Debug/llc.o: In function `ForceCodegenLinking': /home/neale/LLVM/llvm/include/llvm/CodeGen/LinkAllCodegenComponents.h:45: undefined reference to `llvm::createBURRListDAGScheduler(llvm::SelectionDAGISel*, bool)'

I tried building LLVM 2.1 with no real target CPU backends enabled, just the C backend, by hacking the configure script slightly: --- /home/foad/llvm/llvm-2.1/configure 2007-09-17 22:37:52.000000000 +0100 +++ configure 2007-12-13 10:29:41.000000000 +0000 @@ -4762,7 +4762,7 @@ done ;; esac -TARGETS_TO_BUILD="CBackend MSIL $TARGETS_TO_BUILD"

I ran with VERBOSE=1 and see: g++ -I/home/neale/LLVM/llvm/include -I/home/neale/LLVM/llvm/tools/llc -D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -g -fno-exceptions -fPIC -Woverloaded-virtual -pedantic -Wall -W -Wwrite-strings -Wno-long-long -Wunused -Wno-unused-parameter -g -Wl,-R -Wl,/home/neale/LLVM/llvm/Debug/bin -Wl,-export-dynamic

Hi Duncan, > (1) on x86-64 linux, gcc 4.1.2: I'm not seeing those in x86-64 with gcc 4.3 on my system. However, I was seeing build failures on x86-32 with gcc 4.1, related to undefined references. These were caused by the -finlines-visibility-hidden introduced by r55557. I reverted that patch, could you check if you're still seeing all these failures? Gr. Matthijs

Hi everyone.I am using the visual stuido 2005 to build the lastesllvm source code. After the building phase, the vs 2005 dump two errors with the lli and llc. Here is the message: the Error 1549 error LNK2019: unresolved external symbol "class llvm::FunctionPass * __cdecl llvm::createPBQPRegisterAllocator(void)" (?createPBQPRegisterAllocator at llvm@@YAPAVFunctionPass at 1@XZ)

Quoting Bill Wendling <isanbard at gmail.com>: > Hi Nikolaos, > > I have an alpha version of Chow & Hennesey's priority-based graph > coloring algorithm. It's suffering from some bit-rotting -- e.g., > there's some trouble with how it calculates "forbidden" registers. > You're welcome to the code, if you'd like to hack on it. I've been

Hi, > (2) on alpha, gcc 4.2.4. The "unknown component name: alphacodegen" > didn't use to occur. My fault, I'll fix it. The problem is that lli wants to link in JIT module, which does not exist for these targets. -- WBR, Anton Korobeynikov

Hi, I wanted to write a new register allocation algorithm. I wrote it the same way RegAllocFast has been written and registered it. I added it to ForceCodegenLinking struct as well. But after build, it is not listed in llc --help. I tried to change the registered name of greedy algorithm to something else and that doesnt seem to be reflecting in llc help either. Am i supposed to build llvm

Hello, Neale > These entry points are in modules that have been compiled and placed into an > archive. (e.g. llvm::createBURRListDAGScheduler is in ScheduleDAGRRList.cpp > whose object is placed in ./Debug/lib/libLLVMSelectionDAG.a). > > I'm sure I've missed a configuration option or something trivial like that > but my newbie brain can't determine what it is. make

This allows the use of shadow stack from the llvm-c API. I am not sure this is the place to insert the include, though. Index: include/llvm-c/ExecutionEngine.h =================================================================== --- include/llvm-c/ExecutionEngine.h (revision 56175) +++ include/llvm-c/ExecutionEngine.h (working copy) @@ -24,6 +24,7 @@ #ifdef __cplusplus extern "C" {

Hi, I wanted to write a new register allocation algorithm. I wrote it the same way RegAllocFast has been written and registered it. I added it to ForceCodegenLinking struct as well. But after build, it is not listed in llc --help. I tried to change the registered name of greedy algorithm to something else and that doesnt seem to be reflecting in llc help either. Am i supposed to build llvm

Welcome to the world of pluggable machine passes. This work was done to lighten the load of some llvm tools, ie., only link in the register allocators and instruction schedulers that are actually needed in a particular circumstance. I guess I will have to write this up, but generally it works like this. In your register allocator .cpp file add the following include; #include

On Sat, 2 Sep 2006, Anton Vayvod wrote: > I didn't manage to link my regalloc to lli (I added USEDLIBS to its > makefile). Without it I can't run tests cause they need lli to be built. So > how can I link createMyRegisterAllocator function to lli? Make sure to add it to Codegen/LinkAllCodegenComponents.h. -Chris > On 8/22/06, Anton Vayvod <avayvod at gmail.com> wrote:

On 9/2/06, Chris Lattner <sabre at nondot.org> wrote: > > Make sure to add it to Codegen/LinkAllCodegenComponents.h. I'm sure I did. I did so from the first time and I also needed to add my library .a file to the USEDLIBS variable within llc makefile to build llc. I wonder how lli links with all the rest LLVM as it seems to include no lib within its makefile. May be I need to

I've completed a survey of llvm for unnecessary dependencies on libstdc++, and on conflicts with the upcoming C++0X standard, and am recommending several changes in the enclosed patch (created with svn diff). Here is a summary of the patch: --- #include <cstdlib> added to LinkAllVMCore.h and LinkAllCodegenComponents.h to declare std::getenv. Changed next(...) to llvm::next(...) in

On Thu, 3 Aug 2006, Jim Laskey wrote: > To force the load/linking of your register allocator into the llc/lli tools, > add your create function's global declaration to "Passes.h" and add a > "pseudo" call line to "llvm/Codegen/LinkAllCodegenComponents.h" . Another note: with this new functionality you should be able to dynamically load register

As you may have noticed, I have been working on a fast register allocator in the last week. The new allocator is intended to replace the local allocator for debug builds. Both allocators use a local allocation strategy. Each basic block is scanned from top to bottom, and virtual registers are assigned to physical registers as they appear. There are no live registers between blocks. Everything is

gc-7-integration.patch (+100 -15): include/llvm/CodeGen/LinkAllCodegenComponents.h (+4) include/llvm/CodeGen/SelectionDAGISel.h (+3 -1) include/llvm/CodeGen/AsmPrinter.h (+4) lib/CodeGen/LLVMTargetMachine.cpp (+23 -4) lib/CodeGen/AsmPrinter.cpp (+19) lib/CodeGen/SelectionDAG/SelectionDAGISel.cpp (+36 -8) lib/CodeGen/README.txt (+5) lib/Target/CBackend/CBackend.cpp (+3 -1)