similar to: [LLVMdev] Link error building llc

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

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

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"

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

I'm seeing a lot of build failures recently: (1) on x86-64 linux, gcc 4.1.2: ... llvm[3]: Compiling Hello.cpp for Debug build (PIC) llvm[3]: Linking Debug Loadable Module LLVMHello.so /usr/bin/ld: .../llvm/build/llvm/lib/Transforms/Hello/Debug/.libs/Hello.o: relocation R_X86_64_PC32 against `std::basic_string<char, std::char_traits<char>, std::allocator<char>

Hi, I am beginning the porting process for Linux on System z (aka IBM Mainframe). I thought I¹d build LLVM first with the c and cpp backends so that tools like TableGen would be created that I¹d then use to process the .td files that I¹ll be creating. So I used svn to grab the code from the repository and ran configure and make. However, the build breaks at this point: llvm[1]: Building

Hi, > llvm[1]: Building Intrinsics.gen.tmp from Intrinsics.td > tblgen: IntrinsicEmitter.cpp:163: void EmitTypeForValueType(std::ostream&, > llvm::MVT::SimpleValueType): Assertion `false && "Unsupported ValueType!"' > failed. this came up before IIRC, but I don't remember the details - buggy system compiler? Try searching the archives. Also, if you

Just got clang from head and getting: ExprConstant.cpp: In function Obool TryEvaluateBuiltinNaN(clang::ASTContext&, clang::QualType, const clang::Expr*, bool, llvm::APFloat&)¹: ExprConstant.cpp:1578: error: no matching function for call to Ollvm::StringRef::getAsInteger(int, llvm::APInt&)¹ /home/neale/LLVM/llvm/include/llvm/ADT/StringRef.h:269: note: candidates are: bool

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

I searched the archives and found this from last month: I ran into the same problem and fixed it by forcing the MVT::SimpleValueType enum to be 64 bits so that all of the types in the union later in the class are the same size. I tested this on ppc64 and x86_64. Index: include/llvm/CodeGen/ValueTypes.h =================================================================== ---

Hello, Neale > -lLLVMBitReader /home/neale/LLVM/llvm/Debug/lib/LLVMCBackend.o > -lLLVMCodeGen -lLLVMScalarOpts -lLLVMTransformUtils -lLLVMipa -lLLVMAnalysis > /home/neale/LLVM/llvm/Debug/lib/LLVMCppBackend.o -lLLVMTarget -lLLVMCore > -lLLVMSupport -lLLVMSystem -lpthread -ldl -lm -lelf It seems, that you did not specify any single backend except C. Please do so. > So it

I have written a managesieve server from scratch in Python. I did just enough work to get it working with avelsieve (the squirrelmail plugin), smartsieve, and KDE's sieve kioplugin. It supports the entire Internet draft. Since I didn't have a working sieve server to compare against, I'm not sure if it's 100% compatible with timsieved. Client applications seem to work okay

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" {

Hello, So the current JIT will be superseded by the MCJIT completely and no further development should be expected for the current JIT? In any case, I am definitely interested in submitting a patch if you could help me by sending me in the right direction, since I really want this working. I managed to reproduce this behavior in LLVM 3.0 by modifying llc to read my .bc file and try to JIT the

Hi I''m new to Rails and I''m struggling with a ''has-one'' relationship. I''m trying to save product and image data in seperate tables with one to one relationship. I''m assuming the problem lies in the controller method below but can''t work it out. The models contain the has_one and belongs to statements, and I tried swapping these

Hi, Were you able to get past this error: make[1]: Entering directory `/builddir/build/BUILD/llvm-2.5/lib/VMCore' llvm[1]: Building Intrinsics.gen.tmp from Intrinsics.td tblgen: IntrinsicEmitter.cpp:137: void EmitTypeForValueType(std::ostream&, llvm::MVT::SimpleValueType): Assertion `false && "Unsupported ValueType!"' failed. make[1]: Leaving directory

Hi Neale, > The comment in the above fix indicates that in this 64-bit system the enum > needs to be 64-bits is correct, but the fix doesn't seem to do it. the basic problem seems to be that your system compiler is miscompiling LLVM. Mucking around with the details of the union in the hope of tricking the compiler into not miscompiling is one approach, but as you saw each broken

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