search for: requires_rtti

...e is no problem under MSVC since rtti seems to be active there anyway). The appropriate line 348 in llvm/makefile.rules is commented out meaning that llvm is usually compiled using rtti. However every clang lib adds -fno-rtti to CXXFLAGS by hand. This is not filtered out by makefile.rules even if REQUIRES_RTTI is defined (IMHO -fno-rtti should be filtered out in that case). Now I'm two-way bewildered. First: why is line 348 commented out? This renders REQUIRES_RTTI useless. Does rtti (llvm) and non-rtti (clang) code work together at all? I had serious trouble when trying this with my own applicati...

...der MSVC since rtti seems to be active there anyway). > The appropriate line 348 in llvm/makefile.rules is commented out meaning > that llvm is usually compiled using rtti. However every clang lib adds > -fno-rtti to CXXFLAGS by hand. > This is not filtered out by makefile.rules even if REQUIRES_RTTI is > defined (IMHO -fno-rtti should be filtered out in that case). > Now I'm two-way bewildered. > First: why is line 348 commented out? This renders REQUIRES_RTTI > useless. Does rtti (llvm) and non-rtti (clang) code work together at > all? I had serious trouble when trying this...

On 04/28/2010 11:42 AM, Yuri wrote: > Looks like this is platform dependent. Yep, works fine here on Debian 5.0/x86_64 with gcc 4.3.2. Did you build with make REQUIRES_RTTI=1 which is required as of LLVM 2.7 to get RTTI for LLVM symbols? -- Pekka

...utils/unittest/UnitTestMain/Makefile index 3082779..7bcb724 100644 --- a/utils/unittest/UnitTestMain/Makefile +++ b/utils/unittest/UnitTestMain/Makefile @@ -11,7 +11,7 @@ LEVEL = ../../.. include $(LEVEL)/Makefile.config -LIBRARYNAME = UnitTestMain +LIBRARYNAME = gtest_main BUILD_ARCHIVE = 1 REQUIRES_RTTI = 1 diff --git a/utils/unittest/googletest/Makefile b/utils/unittest/googletest/Makefile index 21b29ff..22c8f36 100644 --- a/utils/unittest/googletest/Makefile +++ b/utils/unittest/googletest/Makefile @@ -11,7 +11,7 @@ LEVEL := ../../.. include $(LEVEL)/Makefile.config -LIBRARYNAME = GoogleT...

Pekka Jääskeläinen wrote: > On 04/28/2010 11:42 AM, Yuri wrote: >> Looks like this is platform dependent. > > Yep, works fine here on Debian 5.0/x86_64 with gcc 4.3.2. > > Did you build with make REQUIRES_RTTI=1 which is required > as of LLVM 2.7 to get RTTI for LLVM symbols? > No. If this is a hack to get the command 'g++ -shared -o libLLVM-2.7.so -lXXX -lXXX -lXXX ...' to actually produce the full shared library this should be done automatically by Makefile and not exposed to the user....

..."undefined reference to `boost::throw_exception(std::exception const&)" When I compile the external code from outside the LLVM Makefile system, everything goes well. Is it possible to enable exception handling for some parts of the compilation? Just like turning on RTTI with "REQUIRES_RTTI=1" ? Removing exception handling from the functions is not an option, since I would have to tweak the Boost library internals. Thanks ahead! -- Pablo Barrio Dpto. Ing. Electrónica - E.T.S.I. Telecomunicación Despacho C-203 Avda. Complutense s/n, 28040 Madrid Tlf. 915495700 ext. 4234 @: pba...

...ti enabled base classes with derived classes that are compiled > with rtti on. > > So could rtti be turned on for default builds of llvm so that we could > continue using (non-customized) llvm libraries for our compiler? Hi Heikki, You should be able to get this by doing "make REQUIRES_RTTI=1" when building LLVM. -Chris

...lt;yuri at tsoft.com> wrote: > Pekka Jääskeläinen wrote: >> >> On 04/28/2010 11:42 AM, Yuri wrote: >>> >>> Looks like this is platform dependent. >> >> Yep, works fine here on Debian 5.0/x86_64 with gcc 4.3.2. >> >> Did you build with make REQUIRES_RTTI=1 which is required >> as of LLVM 2.7 to get RTTI for LLVM symbols? >> > > No. > If this is a hack to get the command 'g++ -shared -o libLLVM-2.7.so -lXXX > -lXXX -lXXX ...' to actually produce the full shared library this should be > done > automatically by Ma...

...to `boost::throw_exception(std::exception const&)" > > When I compile the external code from outside the LLVM Makefile system, > everything goes well. Is it possible to enable exception handling for > some parts of the compilation? Just like turning on RTTI with > "REQUIRES_RTTI=1" ? Removing exception handling from the functions is > not an option, since I would have to tweak the Boost library internals. Whatever the LLVM side of things, boost::throw_exception is a function that you, the user, have to implement when disabling exceptions. It's basically the &...

...ual const llvm::TargetFrameLowering::SpillSlot* llvm::PPCFrameLowering::getCalleeSavedSpillSlots(unsigned int&) const’: PPCFrameLowering.h:138:51: error: ‘X31’ is not a member of ‘llvm::PPC’ I'm using the same configure I did for 3.2 (well, I didn't explicitly set gcc before): export REQUIRES_RTTI=1 export REQUIRES_EH=1 export CC=gcc export CXX=g++ ./configure --prefix=/opt/llvm/install --enable-optimized --enable-shared --enable-libffi --enable-assertions --enable-doxygen Then I just run: make -- edA-qa mort-ora-y -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- S...

...ons \ --enable-optimized \ --enable-targets=x86,x86_64 --enable-profiling \ make REQUIRES_RTTI=1 sudo make install According to previous posts to the list, REQUIRE_RTTI=1 should do, but I still get a lot of RTTI-related errors like this while linking "opt": (.data.rel.ro._ZTIN4llvm10X86JITInfoE[typeinfo for llvm::X86JITInfo]+0x10): undefined reference to `typeinfo for llvm::Tar...

Jeffrey Yasskin wrote: > I just tried it again on trunk (not 2.7) on OSX 10.5, and it works. > What platform are you on? Does it work with another version of gcc? > Looks like this is platform dependent. libLLVM-2.7.so created has size only 4145 bytes and all llvm symbols are missing. It's empty because there are no .o modules included into it, only libraries through -l options

..., I'd appreciate their expertise. This was really irritating to me as well, when I was trying to to eliminate RTTI. The best advice I can give is that it is best to stop using RTTI (and EH) in any of your code if possible. If you want to build LLVM with full rtti support, you can add a REQUIRES_RTTI=1 setting to the top level Makefile.config or on the make command line. -Chris

...w_exception(std::exception const&)" >> >> When I compile the external code from outside the LLVM Makefile system, >> everything goes well. Is it possible to enable exception handling for >> some parts of the compilation? Just like turning on RTTI with >> "REQUIRES_RTTI=1" ? Removing exception handling from the functions is >> not an option, since I would have to tweak the Boost library internals. > Whatever the LLVM side of things, boost::throw_exception is a function that you, the user, have to implement when disabling exceptions. It's basicall...

We at Tampere University of technology are using LLVM for high-level optimizations in the compiler for our TTA processor toolkit(TCE) We have a llvm backend which creates our own intermediate code, and our own instruction selector after that (as LLVM's machine code cannot represent the actual machine codes of our processors). This makes our llvm backend quite different from the ordinary

...>> > > This was really irritating to me as well, when I was trying to to > eliminate RTTI. The best advice I can give is that it is best to stop > using RTTI (and EH) in any of your code if possible. If you want to > build LLVM with full rtti support, you can add a REQUIRES_RTTI=1 > setting to the top level Makefile.config or on the make command line. > On a related note, building googletest with gcc-4.4 doesn't require RTTI, while building it with gcc-4.2 does require RTTI (due to tr1/functional using typeid). I'd be happy if there was a solution for t...

...like your shared library is not being compiled with symbols. > Did you verify that your sources are compiled with -g? I think so, this is the makefile (based on the one in the Hello pass): > LEVEL = ../../.. > LIBRARYNAME = CGF > LOADABLE_MODULE = 1 > USEDLIBS = > > ifneq ($(REQUIRES_RTTI), 1) > ifneq ($(REQUIRES_EH), 1) > EXPORTED_SYMBOL_FILE = $(PROJ_SRC_DIR)/CGF.exports > endif > endif > > include $(LEVEL)/Makefile.common and this is the invocation: > cafxx at ubuntu:~/Projects/llvm2/lib/Transforms/cgf$ make > llvm[0]: Compiling CGFPass.cpp for Debug+Asser...

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

On 02/17/2010 09:58 PM, Chris Lattner wrote: > You should be able to get this by doing "make REQUIRES_RTTI=1" when building LLVM. What is the main reason RTTI is now disabled by default? We discussed this briefly in IRC but could not reach a proper conclusion and I was directed to ask here for the proper reason against it. Having RTTI support in should not have execution speed penalties, only usi...

Hi all, The good news: RC2 testing was successful in that it uncovered a bad regression from 2.8 (which existed in top-of-tree). It also showed that there was an unincorporated fix that needed to go into the clang branch. The bad news: I'm truncating the RC2 testing phase and announcing the RC3 testing phase. Hopefully, because we caught the bugs in time this phase won't impact the