search for: typeinfo

...about POSIX paths: http://cygwin.com/cygwin-ug-net/using.html#using-pathnames Cannot export Rcpp::Vector<14>::update(): symbol not defined Cannot export Rcpp::Vector<14>::~Vector(): symbol not defined Cannot export Rcpp::Vector<14>::~Vector(): symbol not defined Cannot export typeinfo for Rcpp::VectorBase<14, true, Rcpp::Vector<14> >: symbol not defined Cannot export typeinfo for Rcpp::Vector<14>: symbol not defined Cannot export typeinfo for Rcpp::traits::expands_to_logical__impl<14>: symbol not defined Cannot export typeinfo for Rcpp::RObject: symbol n...

...th 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 llvm::CmpInst' libqdp.a(qdp_jit_util.o):(.rodata._ZTIN4llvm16ExtractValueInstE[_ZTIN4llvm16ExtractValueInstE]+0x10): undefined reference to `typeinfo for llvm::UnaryInstruction' libqdp.a(qdp_jit_util.o):(.rodata._ZTIN4llvm15InsertValueInstE[_ZTIN4llvm15InsertValueInstE]+0x10): undefin...

...testtesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttest' truncated to 255 bytes in column 'v2' Some search of the R-Help Archives yielded a possible solution, http://tolstoy.newcastle.edu.au/R/help/06/05/28088.html defining the typeInfo argument... typeInfo <- getSqlTypeInfo("EXCEL") typeInfo$character <- "varchar(3000)" z <- odbcConnectExcel2007("test_rodbc.xlsx",readOnly=FALSE) sqlSave(z,d,tablename="Sheet2",rownames=FALSE,typeInfo=typeInfo) odbcClose(z) Error in sqlSave(z, d, t...

.... I have to warn you that in previous releases, it's still pretty experimental; Doug Gregor has done a lot of work on it on ToT. Another option is to run 'nm' on the objects/executables you're interested in. For example, this file: daysthatwere clang$ cat red.cpp #include <typeinfo> struct A {}; struct B { virtual ~B(); }; struct C { virtual ~C(); }; C::~C() {} const std::type_info &test0() { return typeid(const char*); } const std::type_info &test1() { return typeid(const char**); } const std::type_info &test2() { return typeid(A); } const st...

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)? Currently I don't know any better way than runtime logging and asserting. Also, what shall we do we external source libraries (like Teigha from Open Design Alliance), where

Le 5 juin 2014 à 00:32, Rafael Espíndola <rafael.espindola at gmail.com> a écrit : > I think the difference is actually in the c++ library. It looks like > libstdc++ changed to always use strcmp of the typeinfo names: > > https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=149964 > > Should we do the same with libc++? What do people think about this issue?

.... I have to warn you that in previous releases, it's still pretty experimental; Doug Gregor has done a lot of work on it on ToT. Another option is to run 'nm' on the objects/executables you're interested in. For example, this file: daysthatwere clang$ cat red.cpp #include <typeinfo> struct A {}; struct B { virtual ~B(); }; struct C { virtual ~C(); }; C::~C() {} const std::type_info &test0() { return typeid(const char*); } const std::type_info &test1() { return typeid(const char**); } const std::type_info &test2() { return typeid(A); } const st...

On Wed, Jun 04, 2014 at 06:32:35PM -0400, Rafael Espíndola wrote: > I think the difference is actually in the c++ library. It looks like > libstdc++ changed to always use strcmp of the typeinfo names: > > https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=149964 > > Should we do the same with libc++? No. It pessimizes correctly behaving code to work around code that violates the ELF ABI. Consider an application that loads plugins with RTLD_LOCAL. Two plugins impleme...

...ri, Jun 13, 2014 at 08:34:03PM +0200, Akim Demaille wrote: > > Le 5 juin 2014 à 00:32, Rafael Espíndola <rafael.espindola at gmail.com> a écrit : > > > I think the difference is actually in the c++ library. It looks like > > libstdc++ changed to always use strcmp of the typeinfo names: > > > > https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=149964 > > > > Should we do the same with libc++? > > What do people think about this issue? As I wrote earlier, the GCC change is plainly wrong and libc++ works exactly as intended. Joerg

...th ./configure --enable-libcpp --enable-cxx11 Currently I'm only using StringRef, SmallVector and FoldingSet, so I only link libLLVMSupport and libLLVMCore. Are they enough or do I need to link something else? 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 with RTTI support by default? If not, how do I enable it? i don't find an option in...

...lib/analysis/libddg-analysis.a -lLLVMBitReader -lLLVMAsmParser -lLLVMAnalysis -lLLVMTarget -lLLVMCore -lLLVMMC -lLLVMObject -lLLVMSupport -ldl -lpthread -lboost_iostreams-mt -Wl,-rpath,/home/sampaio/llvm/lib: CMakeFiles/cdag_disk.dir/cdag_disk.cxx.o:(.data.rel.ro._ZTIN4llvm2cl15OptionValueCopyISsEE[typeinfo for llvm::cl::OptionValueCopy<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]+0x10): undefined reference to `typeinfo for llvm::cl::GenericOptionValue' ../../lib/analysis/libddg-analysis.a(Ids.cxx.o):(.data.rel.ro._ZTIN3ddg3IdsE[typeinfo for ddg...

...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 MyASTConsumer]+0x10): undefined reference to `typeinfo for clang::ASTConsumer' collect2: ld returned 1 exit status make[3]: *** [extract_interface] Error 1 make[3]: Leaving directory `/home/tang.kk/ppcg/ppcg/isl/interface' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory...

> -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Óscar Fuentes > > Vladimir Pouzanov <farcaller at gmail.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

Gordon Keiser <gkeiser at arxan.com> writes: > There is (was?) a CMake variable for this if you're going that route. > Setting LLVM_REQUIRES_RTTI=1 enabled an RTTI build that I haven't had > issues with. I don't know what the ./configure equivalent is, sorry. LLVM_REQUIRES_RTTI is an internal variable. It works as you say, but there is no guarantee about it. Adding a

...PM +0200, Akim Demaille wrote: > > > > Le 5 juin 2014 à 00:32, Rafael Espíndola <rafael.espindola at gmail.com> a > écrit : > > > > > I think the difference is actually in the c++ library. It looks like > > > libstdc++ changed to always use strcmp of the typeinfo names: > > > > > > https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=149964 > > > > > > Should we do the same with libc++? > > > > What do people think about this issue? > > As I wrote earlier, the GCC change is plainly wrong and libc++...

...int main() > { > try { > throw 34; > } > catch (int) { > } > catch (char) { > } > catch (bool) { > } > } The action is 0x5, this refers to 123 .byte 0x3 124 .byte 0x7d where 0x3 means that the typeinfo is _ZTIi (int). The 0x7d says that if the typeinfo doesn't match, then the next action to consider is at offset -3 from here. In other words, it will continue with 121 .byte 0x2 122 .byte 0x7d i.e. it will then try and match with _ZTIc. If this doesn't matc...

On Mon, Nov 2, 2015 at 8:38 AM, Adrian Prantl via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Looking at the code in clang CGDebugInfo just passes through the width of > the type as it is described by the TypeInfo, which in turn is defined by > the Target. At the moment I do not understand why an x86_fp80 is reported > to be 128 bits wide. (Since it’s a type natively supported by LLVM > http://llvm.org/docs/LangRef.html#floating-point-types I would have > expected it to be more like size=80, alig...

...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 > MyASTConsumer]+0x10): undefined reference to `typeinfo for > clang::ASTConsumer' > collect2: ld returned 1 exit status [snip] So you define a class MyAstConsumer that derives from clang::ASTConsumer and then the link fails because the typinfo for MyAstConsumer can not reference...

...7, and Windows 8 (Release Preview), always the same messages. Error message: $ clang++ -g -O3 toy.cpp `llvm-config --cppflags --ldflags --libs core jit nati ve` -o toy c:/llvm/llvminstall/lib/libLLVMCore.a(Instructions.cpp.obj): duplicate section ` .rdata$_ZTSN4llvm10ilist_nodeINS_11InstructionEEE[typeinfo name for llvm::ilist_ node<llvm::Instruction>]' has different size c:/llvm/llvminstall/lib/libLLVMCore.a(Instructions.cpp.obj): duplicate section ` .rdata$_ZTIN4llvm10ilist_nodeINS_11InstructionEEE[typeinfo for llvm::ilist_node< llvm::Instruction>]' has different size c:/llvm/ll...

I'm in the process of teaching the Verifier to validate that the size of debug info variable and the described value matches (already caught a couple of bugs, both in my frontend and in LLVM itself). However, I've run into the following: size of passed value (80) does not match size of declared variable (128) call void @llvm.dbg.declare(metadata x86_fp80* %x, metadata !11, metadata