search for: type_info

...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 std::type_info &test3() { return typeid(B); } const std::type_info &test4() { return typeid(C); } daysthatwe...

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

...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 std::type_info &test3() { return typeid(B); } const std::type_info &test4() { return typeid(C); } daysthatwe...

...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 std::type_info &test3() { return typeid(B); } const std::type_info &test4() { return typeid(C); } daysthatwe...

...some syntax errors gcc allowed. Linking ran into a single multiple definition error: d:/super/dump/mingw/mingw/bin/../lib/gcc/mingw32/4.4.0/libstdc++.a(tinfo.o):C:\MinGW\src\gccbf\mingw32\libstdc++-v3\libsupc++/../../../../gcc-4.4.0/libstdc++-v3/libsupc++/tinfo.cc:40: multiple definition of `std::type_info::operator==(std::type_info const&) const' objs/test/LoadSave.o:fake:(.text$_ZNKSt9type_infoeqERKS_[std::type_info::operator==(std::type_info const&) const]+0x0): first defined here This seemed to be defined in the libstdc++, and also in each of my Translation Units. I used gcc version...

...5-14 13:44:25.000000000 +0200 @@ -3238,13 +3238,14 @@ static int ptwr_emulated_update( /* We are looking only for read-only mappings of p.t. pages. */ ASSERT((l1e_get_flags(pte) & (_PAGE_RW|_PAGE_PRESENT)) == _PAGE_PRESENT); + ASSERT(mfn_valid(mfn)); ASSERT((page->u.inuse.type_info & PGT_type_mask) == PGT_l1_page_table); ASSERT((page->u.inuse.type_info & PGT_count_mask) != 0); ASSERT(page_get_owner(page) == d); /* Check the new PTE. */ nl1e = l1e_from_intpte(val); - if ( unlikely(!get_page_from_l1e(gl1e_to_ml1e(d, nl1e), d)) ) + if ( unl...

Hi Peter, Thanks for the reply. I agree that the base class vtable may be not referenced by a derived class. However, the vtable of a derived class has to reference its parent type_info, and so having type_info internalized means that the class is final, doesn’t it? Thanks, Nikolai From: Peter Collingbourne [mailto:peter at pcc.me.uk] Sent: Wednesday, December 6, 2017 4:36 AM To: Gainullin, Artur <artur.gainullin at intel.com> Cc: llvm-dev at lists.llvm.org Subject: Re: Qu...

Hi, --- background ---------------------------------------------------- * what the makedumpfile is: To shorten the size of the dumpfile and the time of creating the dumpfile, makedumpfile copies only the necessary pages for analysis to the dumpfile from /proc/vmcore. You can specify the kind of unnecessary pages with dump_level. If you want to shorten the size further, enable the

u.inuse.type_info is at the end of the pfn_info structure, and is u32 for both x86_32 and x86_64--in this location it can also be the last 32 bits of a page. several functions use bitopts.h functions to manipulate this member, and on x86_64 these functions use u64 instructions, which will overflow the page boundary...

On 30 Aug 2013, at 19:42, Duncan Sands <baldrick at free.fr> wrote: > First off, is libc++ supposed to be incompatible with > libstdc++? libc++ does not, and never had, ABI compatibility with libstdc++ as a goal. Actually, libstdc++ periodically breaks ABI compatibility too, as we have recently found in the FreeBSD ports tree with certain projects requiring a newer libstdc++ than

...compilation error or warning is generated). Jeff Cohen wrote: > This may be the case with GCC, but VC++ allows exception handling to > be enabled while RTTI is disabled. According to VC++ documentation, > RTTI is needed only to support dynamic_cast, the typeid operator, and > the type_info class. > > Chris Lattner wrote: > >> On Thu, 21 Apr 2005, Jeff Cohen wrote: >> >>> That's a good point. >> >> >> >> I think there are some issues with doing this (e.g. EH doesn't work, >> so the very few places we use it would hav...

...-DLLVM_LIBDIR_SUFFIX=64 \ -DCLANG_DEFAULT_CXX_STDLIB=libc++ \ -DLLVM_ENABLE_LIBCXX=ON .. results in the following build error: ../projects/compiler-rt/lib/ubsan/ubsan_type_hash_itanium.cc:233: error: undefined reference to 'typeinfo for std::type_info' ../projects/compiler-rt/lib/ubsan/ubsan_type_hash_itanium.cc:233: error: undefined reference to 'typeinfo for __cxxabiv1::__class_type_info' ../projects/compiler-rt/lib/ubsan/ubsan_type_hash_itanium.cc:233: error: undefined reference to '__dynamic_cast' [...] Looks like ubsan...

This patch series includes a series of bugs related to p2m, ept, and PoD code which were found as part of our XenServer product testing. Each of these fixes actual bugs, and the 3.4-based version of the patch has been tested thoroughly. (There may be bugs in porting the patches, but most of them are simple enough as to make it unlikely.) Each patch is conceptually independent, so they can each

...-DCLANG_DEFAULT_CXX_STDLIB=libc++ \ >> -DLLVM_ENABLE_LIBCXX=ON .. >> >> results in the following build error: >> >> ../projects/compiler-rt/lib/ubsan/ubsan_type_hash_itanium.cc:233: >> error: undefined reference to 'typeinfo for std::type_info' >> ../projects/compiler-rt/lib/ubsan/ubsan_type_hash_itanium.cc:233: >> error: undefined reference to 'typeinfo for >> __cxxabiv1::__class_type_info' >> ../projects/compiler-rt/lib/ubsan/ubsan_type_hash_itanium.cc:233: >> error: undefined reference to '...

...-by:Xiaofeng Ling <xiaofeng.ling@intel.com> diff -r 90d9dff47692 -r 188b619dad29 xen/arch/x86/shadow.c --- a/xen/arch/x86/shadow.c Tue Nov 29 09:44:46 2005 +0800 +++ b/xen/arch/x86/shadow.c Tue Nov 29 09:44:46 2005 +0800 @@ -1333,7 +1333,7 @@ i = (frame_table[readonly_gmfn].u.inuse.type_info & PGT_va_mask) >> PGT_va_shift; - if ( (i >= 0 && i <= L1_PAGETABLE_ENTRIES) && + if ( (i >= 0 && i < L1_PAGETABLE_ENTRIES) && !l1e_has_changed(pt[i], match, flags) && fix_entry(...

This may be the case with GCC, but VC++ allows exception handling to be enabled while RTTI is disabled. According to VC++ documentation, RTTI is needed only to support dynamic_cast, the typeid operator, and the type_info class. Chris Lattner wrote: > On Thu, 21 Apr 2005, Jeff Cohen wrote: > >> That's a good point. > > > I think there are some issues with doing this (e.g. EH doesn't work, > so the very few places we use it would have to be modified), but other > than that I ful...

On Thu, 21 Apr 2005, Jeff Cohen wrote: > That's a good point. I think there are some issues with doing this (e.g. EH doesn't work, so the very few places we use it would have to be modified), but other than that I fully support the idea. -Chris > Evan Jones wrote: > >> On Thu, 2005-21-04 at 19:43 -0700, Reid Spencer wrote: >> >>> In case it wasn't

> 2) When I unwind, the stack gets popped but it would make sense to pass some > data to the exception handler. I guess I could use a global variable for > this, but is there a way to do it on the stack? (Wouldn't that make more > sense also?) Passing extra info on the stack doesn't make much sense because the stack gets popped... Also, note that the unwind instruction is

Hi all, Sorry to bother you guys with this question coming from a young beginner, but even after some hours of research, I could not find any way to solve my issue... I have a project using LLVM APIs (3.7.0), so I compile it with options suggested by 'llvm-config -cxxflags', including -fno-rtti. Without this latter option, the build fails ("no reference to typeinfo...").

...nerated). > > Jeff Cohen wrote: > > > This may be the case with GCC, but VC++ allows exception handling to > > be enabled while RTTI is disabled. According to VC++ documentation, > > RTTI is needed only to support dynamic_cast, the typeid operator, and > > the type_info class. > > > > Chris Lattner wrote: > > > >> On Thu, 21 Apr 2005, Jeff Cohen wrote: > >> > >>> That's a good point. > >> > >> > >> > >> I think there are some issues with doing this (e.g. EH doesn't work, &...