<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Sep 30, 2011, at 10:16 AM, Garrison Venn wrote:</div><div><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>On Sep 30, 2011, at 12:15, Somorjai, Akos wrote:</div><div><div><div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 13px; font-family: Arial, sans-serif; "><div><div><div>Hello all,</div><div><br></div><div>I was wondering how llvm and clang handles the RTTI shared libraries issue mentioned here: <a href="http://gcc.gnu.org/faq.html#dso">http://gcc.gnu.org/faq.html#dso</a></div><div><br></div><div>Is it using name or address comparison?</div><div><br></div><div>We have an architecture with several frameworks and plug-ins; some of the latter are being loaded and unloaded runtime.</div><div>In the past that issue caused crashes in our app, so at the moment we are overriding __dynamic_cast to detect this problem, but that's kind of messy. I'm hoping for a better solution with llvm…</div><div><br></div><div>(Mac OS X 10.6/10.7, clang 3.0)</div></div></div></div></blockquote></div></div></div></div></blockquote><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div><div><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 13px; font-family: Arial, sans-serif; "><div><div><div><div><div><br></div></div></div></div></div></div></blockquote></div></div></div></div></div><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">LLVM does not use RTTI--it has its own mechanisms; see llvm/include/llvm/Support/Casting.h, and by default it is turning off for an LLVM build.</div></blockquote><div><br></div>I don't think that's what the OP meant.</div><div><br></div><div>I think he's talking about using RTTI in his code - how LLVM generated code (and/or LLVM runtime libraries) handle RTTI.</div><div>I expect the answer is "The same as gcc, since code compiled with LLVM needs to interoperate with code compiled with gcc.</div><div><br></div>[ I too would like a better way of handling RTTI and dynamic libraries ]<div><br></div><div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Lucida Grande'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">-- Marshall<br><br>Marshall Clow Idio Software <<a href="mailto:mclow.lists@gmail.com">mailto:mclow.lists@gmail.com</a>><br><br>A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait).<br> -- Yu Suzuki</span>
</div>
<br></div></body></html>