search for: rtty

Hi @llvm, I've already asked the following questions to the clang dev list but got no response. Maybe there is a wider audience at llvmdev and someone here can help me. The question actually boils down to: How can I compile clang with rtti enabled? And this was my original mail (with some points now better explained) to clang: <--BEGIN--> Hi @clang, I'm somewhat puzzled about

Hi Olaf, On Fri, Sep 11, 2009 at 5:24 AM, Olaf Krzikalla <Olaf.Krzikalla at tu-dresden.de> wrote: > Hi @clang, > > I'm somewhat puzzled about using rtti when building clang under gcc (gcc > 4.3.3, linux/ubuntu). > (There 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 >

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

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

Hi everyone, I just had a question - I am aware that LLVM supports it's own form of RTTI ( using dyn_cast<>() ,etc) but I wish to use C++ RTTI currently. I have tried building with "cmake -G "Unix Makefiles" -LLVM_ENABLE_RTTI=ON" but that doesnt seem to remove the "fno-rtti" flag from llvm-config and I still get an error when I try using

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

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

Mangled names can be long indeed, but pretty-printed types are also long. I can evaluate effect on size on clang codebase itself. If you disable RTTI, than obviously you can't use it. So if RTTI is disabled, we can disable mangled names in DWARF. Clang is compiled without standard C++ RTTI because it has it's own RTTI. In general, however, many libraries use standard RTTI. 2018-03-02

On Feb 17, 2010, at 3:15 AM, Heikki Kultala wrote: > LLVM 2.7 is dropping rtti on default build, which is a problem to us. > We are using Boost libraries on many places in our code, and Boost has > some heavy usage of type info tricks, which cannot be compiled without > rtti, so we have to keep rtti on for our code. > > But our code also implements the llvm backend framework

Chris Lattner wrote: >> Mainly this is about a nuisance to need to ask users of TCE to recompile >> LLVM (which might be even installed from a precompiled binary for their >> distro) to be able to compile TCE. > > I'm dubious that doing that would actually work anyway. Since LLVM doesn't > provide a stable API, being able to reuse a previously installed

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

Here is result of experiment: (Original size , with DW_AT_linkage_name for composites, % increase) clang-7.0 1926574256 1952846192 1.4% clang-tidy 1220980360 1238498112 1.4% llvm-mt 7404728 7525328 1.6 % std::cout << "hello world!" 21552 22080 2.4 % IMO, not that big price for reliable dynamic type identification (Full disclosure: I need depend on this feature, since

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

Hi, I'm trying to port a piece of code using LLVM as a library to the latest SVN version. 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

On Thu, Oct 14, 2010 at 4:09 PM, Duncan Sands <baldrick at free.fr> wrote: > Hi Francois, > >> In that case, RTTI and exception should also be disabled from CMake >> generated projects right? >> Currently they are enabled all over my MSVC projects. > > I'm not sure what you are asking.  The goal is for LLVM to not require > RTTI or exception handling.

Forgot to CC the list, sorry. ----- Forwarded Message ----- > From: Samuel Crow <samuraileumas at yahoo.com> > To: FlyLanguage <flylanguage at gmail.com> > Cc: > Sent: Monday, July 18, 2011 10:40 AM > Subject: Re: [LLVMdev] RTTI gone in 3.0? > > Hi FlyLanguage, > > I thought LLVM disabled RTTI a long time ago.  It was just too slow. > > --Sam >

On Thu, Feb 18, 2010 at 3:42 PM, Pekka Jääskeläinen <pekka.jaaskelainen at tut.fi> wrote: >  From now on these users need to recompile LLVM from sources with non-default > flags to make TCE (or other external projects using both LLVM and RTTI) to > be able to link with it. I think this should matter something in comparison to > a 5% disk size reduction which can be still achieved

Hi Francois, > In that case, RTTI and exception should also be disabled from CMake > generated projects right? > Currently they are enabled all over my MSVC projects. I'm not sure what you are asking. The goal is for LLVM to not require RTTI or exception handling. Thus these can be disabled by the build system (by specifying -fno-rtti etc), since they won't be used anyway. Not

In that case, RTTI and exception should also be disabled from CMake generated projects right? Currently they are enabled all over my MSVC projects. On Thu, Oct 14, 2010 at 3:57 AM, Duncan Sands <baldrick at free.fr> wrote: > Hi Al, > >> It's good that llvm/lib builds with exceptions and RTTI disabled as it >> supports doing optimization and codegen on very constrained