<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Oct 10, 2018, at 17:05, Eric Fiselier <<a href="mailto:eric@efcs.ca" class="">eric@efcs.ca</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class="">Hi All,<div class=""><br class=""></div><div class="">The status quo of libc++abi and libc++ requires the duplication of a lot of code and logic between the repositories, and often in ways that require the two be kept in perfect sync. As it stands now, this it too complicated. This email proposes putting libc++abi and libc++ into the same repository.</div><div class=""><br class=""></div><div class="">Before I go any further, I want to clarify what I'm NOT PROPOSING.</div><div class=""><br class="">I'm NOT proposing removing support for using libsupc++, libstdc++, or libcxxrt as the runtime library under libc++. I'm NOT proposing absorbing libc++abi into libc++; they will remain distinct entities. In summary, If you use libc++ or libc++abi in a weird configuration today, then that should continue to work after this change.</div><div class=""><font size="4" class=""><br class=""></font></div><div class=""><font size="4" class="">The Problem</font></div><div class=""><font size="4" class="">==========</font></div><div class=""><br class=""></div><div class="">So why do I want to keep the two libraries together? Because the amount of duplication across libc++ and libc++abi is becoming unmaintainable, and that's causing bugs.</div><div class=""><br class=""></div><div class="">For example, libc++abi shipped a serious regression in the 7.0 release which caused thrown exceptions to have the wrong alignment, and in turn caused programs to segfault. It was caused because libc++abi forgot to define _LIBCPP_BUILDING_LIBRARY like libc++ does [1][2]. In the above case a bug was caused because libc++abi depended on libc++ internals, but it was not kept in sync with changes to libc++.</div><div class=""><br class=""></div><div class="">The goal of the merge is to prevent bugs like this from happening in the future.</div></div></div></div></div></div></div></blockquote><div><br class=""></div><div>Maybe the problem is instead that libc++abi _was_ relying on internals of libc++? It’s not clear to me this would be solved by moving the code closer to each other.</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div class=""><br class=""></div><div class="">libc++ and libc++abi also contain duplicate versions of large amounts of code, including the cpp files which implement <new>, <stdexcept>, <exception>, and <typeinfo>. The versions in libc++ and libc++abi should be *the exact same*, but we're forced to keep them in separate repositories. This causes bugs where one version isn't updated when the other gets a new feature or a bug fix [3].</div></div></div></div></div></div></div></blockquote><div><br class=""></div><div>What’s the rationale for needing that code in both libc++ and libc++abi?</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div class=""><br class=""></div><div class="">Finally, libc++ and libc++abi could share almost all of their CMake and LIT configuration, but they don't. This introduces a serious but unneeded maintenance cost. Here's an example from today where the libc++ sanitizer configuration for Mac had to be copied into libc++abi verbatim. [4]</div></div></div></div></div></div></div></blockquote><div><br class=""></div><div>Fair enough.</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div class=""><font size="4" class=""><br class=""></font></div><div class=""><font size="4" class="">Solutions</font></div><div class=""><font size="4" class="">=======</font></div><div class=""><br class=""></div><div class="">I propose merging the libc++ and libc++abi repositories into one. The exact structure of this merged repository is TBD. For simplicity I'll assume we decide to move libc++abi INTO libc++.</div><div class=""><br class=""></div><div class="">There are some open questions:</div><div class=""><br class=""></div><div class=""><ol class=""><li class="">Should we create a new repository for this purpose? Or is it better to use libc++ as shared home (I vote for using libc++).<br class=""><br class=""></li><li class="">Should we do the same for libunwind?<br class=""><br class=""></li><li class="">We want to be able to build libc++ w/o libc++abi, but is the reverse true? Does anybody have an existing use case for building libc++abi w/o libc++?</li></ol></div></div></div></div></div></div></div></blockquote><div>Why does libc++abi require libc++? It seems like this is a rather unfortunate circular dependency.</div><div><br class=""></div><div>I don’t know whether I’m in favor of this move or not. I’m certainly seeing the cost that Eric is depicting, and I’m paying for it, but I need to better understand why things are the way they are currently before formulating an opinion.</div><div><br class=""></div><div>Louis</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div class=""><br class=""></div><div class="">I look forward to the discussion this generates.</div><div class=""><br class=""></div><div class="">[1] <a href="http://llvm.org/PR39051" class="">llvm.org/PR39051</a></div><div class="">[2] Fix for PR39051 - <a href="https://github.com/llvm-mirror/libcxxabi/commit/ed902ff267148f3d76d33283766613056f57a06f" class="">r242815</a></div><div class="">[3] Copying libc++'s new into libc++abi - <a href="https://github.com/llvm-mirror/libcxxabi/commit/4bf15a00704552100c7ffcf92e93c8d3414c9b50" class="">r296787</a></div><div class="">[4] Duplicating more CMake configuration - <a href="https://github.com/llvm-mirror/libcxxabi/commit/6d635f5765e76c66d31a26cb4d5d5e802e274b4f" class="">r344191</a></div><div class=""><br class=""></div><div class=""><br class=""></div></div></div></div></div></div>
</div></blockquote></div><br class=""></body></html>