search for: type_infos

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

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

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

John, I'm trying to use this warning to check the vtable problem. Here's an example In mem.hpp class AA { // Construction / destruction: protected: AA (); AA (const AA&); // Disabled public: virtual ~AA (); }; In mem.cpp #include "mem.hpp" AA::~AA() { } And I still get the following warning: warning: 'AA' has no out-of-line virtual method

I managed to build clang on mingw/msys today. Running configure, make install worked for both debug and optimized builds in general. However there were a few hitches along the way. Make would fail with: ln: creating symbolic link `/d/super/dump/code/llvm/llvm-project/llvm/build.clang/Release+Asserts/bin/clang++.exe' to `clang.exe': No such file or directory ln: creating symbolic link

Make sure MFN read from pte is valid before accessing the page info structure associated with it. Drop guest-to-machine-physical translation from ptwr code. Signed-off-by: Jan Beulich <jbeulich@novell.com> Index: 2007-05-14/xen/arch/x86/mm.c =================================================================== --- 2007-05-14.orig/xen/arch/x86/mm.c 2007-05-14 13:43:50.000000000 +0200 +++

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,

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, and possibly the end of memory as we see here: (XEN)

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

As far as I can tell, exceptions work just fine without RTTI when using gcc 3.4.2. dynamic_cast, on the hand, crashes without RTTI (no 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

Hi, Trying to compile llvm with the following configuration on Linux x86-64: cmake -G Ninja -DBUILD_SHARED_LIBS=ON \ -DCMAKE_SHARED_LINKER_FLAGS="-fuse-ld=gold" \ -DCMAKE_EXE_LINKER_FLAGS="-fuse-ld=gold"\ -DCMAKE_BUILD_TYPE=RelWithDebInfo ' \ -DCMAKE_C_FLAGS="-O2 -g" \

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

Hi, I see the following variables in the CMakeCache.txt: SANITIZER_CXX_ABI:STRING=default //STRINGS property for variable: SANITIZER_CXX_ABI SANITIZER_CXX_ABI-STRINGS:INTERNAL=none;default;libcxxabi;libstdc++ Regards, ismail On Tue, Aug 1, 2017 at 7:32 PM, Vedant Kumar <vsk at apple.com> wrote: > >> On Aug 1, 2017, at 7:07 AM, İsmail Dönmez via llvm-dev <llvm-dev at

# HG changeset patch # User Xiaofeng Ling <xiaofeng.ling@intel.com> # Node ID 188b619dad2998f0625b247ee298def1919696ca # Parent 90d9dff476923318f34c993016c9ada8979ee06d small fix for shadow Signed-off-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 +++

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

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...").

My understanding is that EH works fine without RTTI. However, we use typeid in LLVM in a few limited spots like lib/VMCore/Pass.cpp Reid. On Sat, 2005-04-23 at 20:12 -0700, Jeff Cohen wrote: > As far as I can tell, exceptions work just fine without RTTI when using > gcc 3.4.2. dynamic_cast, on the hand, crashes without RTTI (no > compilation error or warning is generated). > >