search for: frtti

...east I think so. > I use dynamic_casts, is -fno-rtti only for typeinfo?) dynamic_cast depends on RTTI. > It sounds strange to me, the same used to apply before, but I didn't > get this error last month with the old setup… > > Any hint? You can try building LLVM with CXXFLAGS=-frtti configure .... CXXFLAGS=-frtti make ... I'm not sure if CXXFLAGS takes precedence over the hard-coded -fno-rtti in the makefiles, though. With the cmake build, you can try as above (but replacing `configure' with `cmake') or, better: cmake -DLLVM_REQUIRES_RTTI=ON ... rest of cmake ar...

I've actually tried to compile both LLVM and my lib with -frtti with same results. On Dec 10, 2012, at 21:57, Jim Grosbach <grosbach at apple.com> wrote: > Llvm typically doesn't build with RTTI enabled. Perhaps that's what you're running into? > > Jim -- Vladimir Pouzanov http://www.farcaller.net/ -------------- next part -----...

Il giorno 18/mar/2013, alle ore 15:14, Óscar Fuentes <ofv at wanadoo.es> ha scritto: > Nicola Gigante <nicola.gigante at gmail.com> writes: > >> The error I get is the following: >> Undefined symbols for architecture x86_64: >> "typeinfo for llvm::FoldingSetImpl", referenced from: >> typeinfo for llvm::FoldingSet<Type> in Program.o

Hello, I get a crash in my program that uses exceptions and the LLVM JIT, even though the exceptions are controlled and thrown/catched in a part that doesn't deal with LLVM. I noticed that llvm-config --cxxflags includes the -fno-exceptions flag. Do I need to throw no exceptions whatsoever in my application to use LLVM JIT? As a minimal example, I modified the code in

...mail.com> writes: > On Dec 10, 2012, at 21:57, Jim Grosbach <grosbach at apple.com> wrote: >> Llvm typically doesn't build with RTTI enabled. Perhaps that's what >> you're running into? >> > I've actually tried to compile both LLVM and my lib with -frtti with > same results. Please show the exact commands you used for building LLVM with RTTI support. It would also help if you repeat your recipe for building LLVM but appending to your `make' command the text "VERBOSE=1" and then show the compiler command line for one .cpp file (li...

Il giorno 18/mar/2013, alle ore 18:47, Óscar Fuentes ha scritto: > > You can try building LLVM with > > CXXFLAGS=-frtti configure .... > CXXFLAGS=-frtti make ... > > I'm not sure if CXXFLAGS takes precedence over the hard-coded -fno-rtti > in the makefiles, though. > > With the cmake build, you can try as above (but replacing `configure' > with `cmake') or, better: > > cmake...

...ded by > the compilation. Is it? In my experience, it isn't. Please show the relevant command generated by your makefile and the associated error message(s). RTTI is an on/off option that changes per LLVM library, so setting -fno-rtti for using LLVM makes no sense. VMCore and Support have -frtti while most of the rest have -fno-rtti. The switch is decided on cmake/modules/LLVMProcessSources.cmake depending on the value of LLVM_REQUIRES_RTTI. [snip]

...> > Is it? In my experience, it isn't. Please show the relevant command > generated by your makefile and the associated error message(s). > > RTTI is an on/off option that changes per LLVM library, so setting > -fno-rtti for using LLVM makes no sense. VMCore and Support have -frtti > while most of the rest have -fno-rtti. The switch is decided on > cmake/modules/LLVMProcessSources.cmake depending on the value of > LLVM_REQUIRES_RTTI. > > > Hello! I'm sorry, because I've already solved the build problem with the mentioned app manually, now it's no...

Hello LLVM-DEV! Recently I think I found a bug in llvm's CMakeLists.(I use llvm 3.1svn and Clang 3.1) I follow the normal way to try to compile an application that utilize both clang and llvm: I ./autogen.sh it, ./configure it and make it. But the make fails. At last I found out the failure is because that the Makefile's CXXFLAGS does not contain -fno-rtti option which is needed by the

...my experience, it isn't. Please show the relevant command >> generated by your makefile and the associated error message(s). >> > >> RTTI is an on/off option that changes per LLVM library, so setting >> -fno-rtti for using LLVM makes no sense. VMCore and Support have -frtti >> while most of the rest have -fno-rtti. The switch is decided on >> cmake/modules/LLVMProcessSources.cmake depending on the value of >> LLVM_REQUIRES_RTTI. >> >> >> Hello! I'm sorry, because I've already solved the build problem with the > mentioned...

...on. One difference between 2.6 and 2.7svn is that `llvm-config --cxxflags` now include -fno-rtti. Since my code does use RTTI information (in non-trivial dynamic_cast), my code can't compile with this. Same goes for -fexceptions. I've tried setting my CXXFLAGS to `llvm-config --cxxflags` -frtti -fexceptions, now my code compiles, but it doesn't link against LLVM, giving error messages like: undefined reference to `typeinfo for llvm::TargetMachine' undefined reference to `typeinfo for llvm::MCAsmInfo' (for classes inherinting from the classes named by the error messages) So,...

Llvm typically doesn't build with RTTI enabled. Perhaps that's what you're running into? Jim On Dec 10, 2012, at 1:27 PM, Vladimir Pouzanov <farcaller at gmail.com> wrote: > Hi all. > > I fully understand that the problem is a bit OT for llvmdev, but I'm stuck for two days now and I really need some direct push. > > To the problem. I have a C++ shared

...t; > On Dec 10, 2012, at 21:57, Jim Grosbach <grosbach at apple.com> wrote: > >> Llvm typically doesn't build with RTTI enabled. Perhaps that's what > >> you're running into? > >> > > I've actually tried to compile both LLVM and my lib with -frtti with > > same results. > > Please show the exact commands you used for building LLVM with RTTI > support. > > It would also help if you repeat your recipe for building LLVM but appending > to your `make' command the text "VERBOSE=1" and then show the compiler...

Good. Copying llvmdev for the record. Vladimir Pouzanov <farcaller at gmail.com> writes: > Sorted it out. > > In the end, the working build commands for me were: > > % export CXXFLAGS=-frtti > % ../llvm-3.1/configure > --prefix=/Users/farcaller/Developer/Active/llvm-src/install-3.1 > --enable-debug-runtime --enable-debug-symbols --disable-docs > --disable-doxygen --enable-shared > % make -j9 REQUIRES_RTTI=1

Hi all. I fully understand that the problem is a bit OT for llvmdev, but I'm stuck for two days now and I really need some direct push. To the problem. I have a C++ shared library, that's working with llvm C++ api. Consider a function: static Object llvm_Target_createMCAsmInfo(Object self, Object tripleName) { llvm::Target target = from_ruby<llvm::Target>(self); char const

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 \

Ah! Think I figured it out -- it's rtti. When I build with -fno-rtti, the spurious symbol disappears. Blargh, that was complicated. I'm going to try an out-of-source cmake build now. So far this has been a soliloquy, hope it helps someone else. ________________________________ From: llvmdev-bounces at cs.uiuc.edu [llvmdev-bounces at cs.uiuc.edu] on behalf of Charles Jacobsen

...;t. Please show the relevant command > >> generated by your makefile and the associated error message(s). > >> > > > >> RTTI is an on/off option that changes per LLVM library, so setting > >> -fno-rtti for using LLVM makes no sense. VMCore and Support have -frtti > >> while most of the rest have -fno-rtti. The switch is decided on > >> cmake/modules/LLVMProcessSources.cmake depending on the value of > >> LLVM_REQUIRES_RTTI. > >> > >> > >> Hello! I'm sorry, because I've already solved the build pr...