search for: teigha

On Sep 30, 2011, at 9:15 AM, Somorjai, Akos wrote: > I was wondering how llvm and clang handles the RTTI shared libraries issue mentioned here: http://gcc.gnu.org/faq.html#dso This is really a Clang question and so belongs on cfe-dev. > Is it using name or address comparison? Clang strives for interoperability with GCC, which means we use address comparison on targets where GCC does.

...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 we don't really have any control? Just being curious, Akos From: John McCall <rjmccall at apple.com<mailto:rjmccall at apple.com>> Date: Fri, 30 Sep 2011 10:22:02 -0700 To: Ákos Somorjai <asomorjai at graphisoft.com<mailto:asomorjai at gra...

Hello all, I was wondering how llvm and clang handles the RTTI shared libraries issue mentioned here: http://gcc.gnu.org/faq.html#dso Is it using name or address comparison? We have an architecture with several frameworks and plug-ins; some of the latter are being loaded and unloaded runtime. In the past that issue caused crashes in our app, so at the moment we are overriding __dynamic_cast to