similar to: [LLVMdev] Help with LLVM 3.2 linking error

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

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 > ld: symbol(s) not found for architecture x86_64 > > Looking at the error the question is: is llvm built

Nicola Gigante <nicola.gigante at gmail.com> writes: > 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

Hello, I'm starting to play with LLVM today and I've trouble compiling it. I'm working under Windows Vista, with the gcc from Cygwin: gcc (GCC) 3.4.4 (cygming special, gdc 0.12, using dmd 0.125) Is LLVM supposed to work with this version of GCC (probably using the -mno-cygwin option to get a Mingw-like behavior)? The LLVM source tree is from the current SVN trunk. Compilation

Function.cpp:167: error: call of overloaded `AddInteger(uint32_t&)' is ambiguous /home/Seb/llvm/include/llvm/ADT/FoldingSet.h:151: note: candidates are: void llv m::FoldingSetImpl::NodeID::AddInteger(int) /home/Seb/llvm/include/llvm/ADT/FoldingSet.h:152: note: void llvm::FoldingSetIm pl::NodeID::AddInteger(unsigned int) /home/Seb/llvm/include/llvm/ADT/FoldingSet.h:153: note: void

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

Nicola Gigante <nicola.gigante at gmail.com> writes: >> Adding an option for enabling RTTI on the cmake build is trivial. Dunno >> about the `configure' build. You can try filing a feature request on >> Bugzilla. > > Ok, I've managed to refactor some code and remove uses of dynamic_cast. > Making my project work without rtti is a good thing anyway, but

I did an update about 1/2 hr ago, and instead of failing to link with -O4, I'm getting an error elsewhere in the compile. I think I need to stop chasing the bleeding edge. pandora 142% svn update At revision 147455. pandora 143% uname -a Darwin pandora.psychiatry.uiowa.edu 10.8.0 Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386 i386 pandora 144%

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 \

Hi all, I am having some some trouble with LLVM 3.8... I built it with GCC 4.8.2 with cmake and no special CXX/C flags. That means in case of GCC that RTTI is switched on, I believe. However, building my MCJIT application against the just built LLVM and linking results in: libqdp.a(qdp_llvm.o):(.rodata._ZTIN4llvm8FCmpInstE[_ZTIN4llvm8FCmpInstE]+0x10): undefined reference to `typeinfo for

Dear llvmers I'm trying to port some code that was written for llvm 3.1 to 3.4.2. I'm having two linking problems and I couldn't find the source of the problem. Usually it is an error for a virtual method not declared. The error starts even when changing llvm version from 3.1 to 3.2. The current line declaring an command line option: ----- static cl::opt<string>

In any case, it seems that GCC 3.4.4 may be in hot water even if you did get it to compile: http://llvm.org/docs/GettingStarted.html#brokengcc -- Christopher Lamb On Aug 6, 2007, at 9:48 AM, Alain Frisch wrote: > Hello, > > I'm starting to play with LLVM today and I've trouble compiling it. > I'm > working under Windows Vista, with the gcc from Cygwin: > >

Hi, Lately LLVM has been adding -fno-rtti to most of the compiler. I have a pass which uses LoopPass and which inherits from FunctionPass and a class of my own. If I compile my code with ENABLE_RTTI=1, I can't dynamically load the shared object since it won't be able to find the symbol for LoopPass's typeinfo. undefined symbol: _ZTIN4llvm8LoopPassE $ c++filt _ZTIN4llvm8LoopPassE

I got your point. Thank you, and I'd like to provide the relative message now. But firstly, what do you mean by the "relevant command generated by your makefile"? What I can tell you now is: The Error Message: make[3]: Entering directory `/home/tang.kk/ppcg/ppcg/isl/interface' CXXLD extract_interface extract_interface.o:(.data.rel.ro._ZTI13MyASTConsumer[typeinfo for

Jun-qi Deng <dengjunqi06323011 at gmail.com> writes: > I got your point. Thank you, and I'd like to provide the relative message > now. But firstly, what do you mean by the "relevant command generated by > your makefile"? What I can tell you now is: > > The Error Message: > make[3]: Entering directory `/home/tang.kk/ppcg/ppcg/isl/interface' > CXXLD

Thanks, John. I'll experiment with both the warning and the nm-weak external tool, and let you know the results. Best, Akos From: John McCall <rjmccall at apple.com<mailto:rjmccall at apple.com>> Date: Fri, 30 Sep 2011 15:24:33 -0700 To: Ákos Somorjai <asomorjai at graphisoft.com<mailto:asomorjai at graphisoft.com>> Cc: "llvmdev at cs.uiuc.edu<mailto:llvmdev

On Jan 28, 2010, at 12:45 PM, Thomas B. Jablin wrote: > Hi, > Lately LLVM has been adding -fno-rtti to most of the compiler. I > have a pass which uses LoopPass and which inherits from FunctionPass > and a class of my own. If I compile my code with ENABLE_RTTI=1, I > can't dynamically load the shared object since it won't be able to > find the symbol for

On Sep 30, 2011, at 3:04 PM, Somorjai, Akos wrote: > Thanks! Yes, we are trying to avoid that situation as much as possible. > > Is there any compiler/linker/static analyzer option that would point out those problems (in 13 million lines, large part of that being legacy code)? There's a -Wweak-vtables which will point out a lot of these cases. I have to warn you that in previous

On 01/29/2010 12:11 AM, Chris Lattner wrote: > On Jan 28, 2010, at 12:45 PM, Thomas B. Jablin wrote: > > >> Hi, >> Lately LLVM has been adding -fno-rtti to most of the compiler. I >> have a pass which uses LoopPass and which inherits from FunctionPass >> and a class of my own. If I compile my code with ENABLE_RTTI=1, I >> can't dynamically load

Hi Trevor, > I've written a CallGraphSCCPass that compiles successfully, but when I > try to run it with opt, it fails: > > Symbol not found: __ZTIN4llvm16CallGraphSCCPassE $ c++filt _ZTIN4llvm16CallGraphSCCPassE typeinfo for llvm::CallGraphSCCPass LLVM TOT has RTTI turned off as far as I know (not sure about 2.7). Are you making use of RTTI? Ciao, Duncan.