search for: s1065342n3h84

Hi Chen, llvm-gcc is dead. Try dragonegg [] or clang [2]. [1] http://dragonegg.llvm.org/ [2] http://clang.llvm.org/ Regards, chenwj -- Wei-Ren Chen (陳韋任) Computer Systems Lab, Institute of Information Science, Academia Sinica, Taiwan (R.O.C.) Tel:886-2-2788-3799 #1667 Homepage: http://people.cs.nctu.edu.tw/~chenwj

Hi all, I'm having problems compiling LLVM 3.2 with RTTI enabled. Since my code makes heavy use of the Boost libraries, RTTI is a must. This is the script I use to compile (as root): SRC_ROOT=$PWD OBJ_ROOT=/export/apps/llvm INSTALL_ROOT=/usr/local mkdir -p $OBJ_ROOT cd $OBJ_ROOT $SRC_ROOT/configure --prefix=$INSTALL_ROOT \

...------------------------- > If you reply to this email, your message will be added to the discussion > below: > > http://llvm.1065342.n5.nabble.com/internal-compiler-error-when-compiling-llvm-gcc-4-2-2-9-tp56010p56013.html > To start a new topic under LLVM - Dev, email > ml-node+s1065342n3h84 at n5.nabble.com > To unsubscribe from internal compiler error when compiling > llvm-gcc-4.2-2.9, click here<http://llvm.1065342.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=56010&code=bGVmdGNvcHkuY2h4QGdtYWlsLmNvbXw1NjAxMHwtMTI3NjY3OTkyNg==> > . >...

Hi, When using llvm-ld to link .bc files(compiled with llvm-gcc with option --emit-llvm), I went into error like: file not recognized: File format not recognized. I was confused because llvm-ld is the LLVM linker to link llvm bitcode files together, then why this error occurred? I am using llvm 2.9 and the corresponding binary version of llvm-gcc. It will be appreciated if anyone of you can

hi, with LLVM 3.1, i am trying to compile toy.cpp from http://llvm.org/docs/tutorial/LangImpl7.html#code. i got the following error: $ clang++ -g toy.cpp `llvm-config --cppflags --ldflags --libs core jit native` -O3 -o toy toy.cpp:4:10: fatal error: 'llvm/IRBuilder.h' file not found #include "llvm/IRBuilder.h" i fixed this by modifying the broken line to: #include

Hi Jin, It's difficult to say just from looking at a pass, but one thing looked odd: > CallInst *call_print = CallInst::Create(call_print,paramArrayRef,"",ins_temp); This looks very dodgy. The "call_print" being used as an argument is the (uninitialised) one that's just been declared. This could be the source of the assertion failure (though a segfault is just as

Hello, everyone! I want to write a pass which can insert a call "printf" instructions before every instruction in the LLVM IR. here is what I wrote: namespace { class call_print : public FunctionPass{ private: DenseMap<const Value*, int> inst_map; public: static char ID; call_print() : FunctionPass(ID){} //define a extern function "printf" static llvm::Function*

Hi everyone, Recently I tried to compile llvm-gcc-4.2-2.9 on a 64bit ubuntu12.04 machine. And I was using the settings below, export C_INCLUDE_PATH=/usr/include/x86_64-linux-gnu export LIBRARY_PATH=/usr/lib/x86_64-linux-gnu ../llvm-gcc-4.2-2.9.source/configure --enable-optimized --program-prefix=llvm- --enable-checking --enable-llvm=${HOME}/moonbox/llvm-obj/Debug+Asserts

Hi everyone, I have some trouble in instrumenting load instructions. I want to instrument load instructions as follow: Firstly, I judge whether the loaded pointer(*any type is possible*) is NULL. If so, I want to explicitly allocate the corresponding address space of its type to the pointer. For example, in source code level I want to translate the next statement *p = 1; into the next