<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jan 4, 2021 at 11:04 AM Tom Stellard <<a href="mailto:tstellar@redhat.com">tstellar@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 1/3/21 1:49 PM, Stella Laurenzo via llvm-dev wrote:<br>
> Hi folks, happy new year!<br>
> <br>
> *Proposal:*<br>
> <br>
> * See comments at the top of LLVMComponents.cmake<br>
> <<a href="https://github.com/stellaraccident/llvm-project/blob/newcomponents/llvm/cmake/modules/LLVMComponents.cmake" rel="noreferrer" target="_blank">https://github.com/stellaraccident/llvm-project/blob/newcomponents/llvm/cmake/modules/LLVMComponents.cmake</a>><br>
> in my fork<br>
> <<a href="https://github.com/stellaraccident/llvm-project/tree/newcomponents" rel="noreferrer" target="_blank">https://github.com/stellaraccident/llvm-project/tree/newcomponents</a>>.<br>
> * Draft phab: <a href="https://reviews.llvm.org/D94000" rel="noreferrer" target="_blank">https://reviews.llvm.org/D94000</a><br>
> <br>
> <br>
> *Background:*<br>
> As I've been working on NPCOMP <br>
> <<a href="https://github.com/llvm/mlir-npcomp" rel="noreferrer" target="_blank">https://github.com/llvm/mlir-npcomp</a>> trying to come up with a release <br>
> flow for MLIR derived Python projects (see py-mlir-release <br>
> <<a href="https://github.com/stellaraccident/mlir-py-release" rel="noreferrer" target="_blank">https://github.com/stellaraccident/mlir-py-release</a>>), I've repeatedly <br>
> run into issues with how the LLVM build system generates shared <br>
> libraries. While the problems have been varied, I pattern match most of <br>
> them to a certain "pragmatic" nature to how components/libLLVM/libMLIR <br>
> have come to be: in my experience, you can fix most individual dynamic <br>
> linkage issues with another work-around, but the need for this tends to <br>
> be rooted in a lack of definition and structure to the libraries <br>
> themselves, causing various kinds of problems and scenarios that don't <br>
> arise if developed to stricter standards. (This isn't a knock on anyone <br>
> -- I know how these things tend to grow. My main observation is that I <br>
> think we have outgrown the ad-hoc nature of shared libraries in the LLVM <br>
> build now).<br>
> <br>
> I think I'm hitting this because reasonable Python projects and releases <br>
> pre-supposes a robust dynamic linkage story. Also, I use Windows and am <br>
> very aware that LLVM basically does not support dynamic linking on <br>
> Windows -- and cannot without more structure (and in my experience, this <br>
> structure would also benefit the robustness of dynamic linking on the <br>
> others).<br>
> <br>
> Several of us got together to discuss this in November <br>
> <<a href="https://llvm.discourse.group/t/meeting-notes-mlir-build-install-and-shared-libraries/2257" rel="noreferrer" target="_blank">https://llvm.discourse.group/t/meeting-notes-mlir-build-install-and-shared-libraries/2257</a>>. <br>
> We generally agreed that BUILD_SHARED_LIBS was closer to what we wanted <br>
> vs libLLVM/libMLIR, but the result is really only factored for <br>
> development (i.e. not every add_library should result in a shared object <br>
> -- the shared library surface should mirror public interface boundaries <br>
> and add_library mirrors private boundaries). The primary difference <br>
> between the two is:<br>
> <br>
> * BUILD_SHARED_LIBS preserves the invariant that every translation<br>
> unit will be "homed" in one library at link time (either .so/.dll or<br>
> .a) and the system will never try to link together shared and static<br>
> dependencies of the same thing (which is what libLLVM/libMLIR do<br>
> today). It turns out that this is merely a good idea on most<br>
> platforms but is the core requirement on native Windows (leaving out<br>
> mingw, which uses some clever and dirty tricks to try to blend the<br>
> worlds).<br>
> * LLVM_BUILD_LLVM_DYLIB treats libLLVM.so as a "bucket" to throw<br>
> things that might benefit from shared linkage, but end binaries end<br>
> up also needing to link against the static libraries in case if what<br>
> you want isn't in libLLVM.so. When this is done just right, it can<br>
> work (on Unix) but it is very fragile and prone to multiple<br>
> definition and other linkage issues that can be extremely hard to<br>
> track down.<br>
> <br>
> *What I did:*<br>
> <br>
> 1. Well, first, I tried looking the other way for a few months and<br>
> hoping someone else would fix it :)<br>
> 2. When I started trying to generalize some of the shared library<br>
> handling for MLIR and NPCOMP, I noted that the LLVM_LINK_COMPONENTS<br>
> (as in named groups of things) are in the right direction of having<br>
> a structure to the libraries, and I found that I could actually<br>
> rebase all of what the LLVM_LINK_COMPONENTS was trying to do on the<br>
> same facility, relegating the existing LLVM_LINK_COMPONENTS to a<br>
> name normalization layer on top of a more generic "LLVM Components"<br>
> facility that enforces stricter layering and more control than the<br>
> old libLLVM.so facility did.<br>
> 3. I rewrote it twice to progressively more modern CMake and was able<br>
> to eliminate all of the ad-hoc dependency tracking in favor of<br>
> straight-forward use of INTERFACE libraries and $<TARGET_PROPERTY><br>
> generator expressions for selecting static or dynamic component<br>
> trees based on global flags and the presence (or absence) of<br>
> per-executable LLVM_LINK_STATIC properties<br>
> 1. Note that since this is rooted only in CMake features and not<br>
> LLVM macros, out of tree, non-LLVM projects should be able to<br>
> depend on LLVM components in their own targets.<br>
> 4. I hacked up AddLLVM/LLVM-Build/LLVM-Config to (mostly) use the new<br>
> facility (leaving out a few things that can be fixed but aren't<br>
> conceptual issues), applied a bunch of fixes to the tree that were<br>
> revealed by stricter checks and got all related tests passing for<br>
> LLVM and MLIR (on X86 -- some mechanical changes need to be made to<br>
> other targets) for both dynamic and static builds.<br>
> <br>
> *What I'd like to do:*<br>
> <br>
> * Get some consensus that we'd like to improve things in this area and<br>
> that the approach I'm taking makes sense. I can do a lot of the<br>
> work, but I don't want to waste my time, and this stuff is fragile<br>
> if we keep it in an intermediate state for too long (I'm already<br>
> paying this price downstream).<br>
> * Land LLVMComponents.cmake<br>
> <<a href="https://github.com/stellaraccident/llvm-project/blob/newcomponents/llvm/cmake/modules/LLVMComponents.cmake" rel="noreferrer" target="_blank">https://github.com/stellaraccident/llvm-project/blob/newcomponents/llvm/cmake/modules/LLVMComponents.cmake</a>><br>
> as the basis of the new facility.<br>
<br>
Do you have a proposed list of components yet for LLVM?<br>
<br>
> * Finish implementing the "Redirection" feature that would allow us to<br>
> emulate an aggregate libLLVM as it is today.<br>
> * Start pre-staging the various stricter constraints to the build tree<br>
> that will be needed to swap AddLLVM to use the new facility.<br>
> * Rewrite component-related AddLLVM/LLVM-Build/LLVM-Config bits in a<br>
> more principled way to use the new facility (or remove features<br>
> entirely that are no longer needed) -- what I did in the above patch<br>
> was just a minimal amount of working around for a POC.<br>
> * Agree on whether we should try to have the two co-exist for a time<br>
> or do a more clean break with the old.<br>
> * Start applying the facility to downstream projects like MLIR and NPCOMP.<br>
> <br>
<br>
It sounds like what you are proposing is BUILD_SHARED_LIBS=ON but with <br>
fewer total libraries, is this an accurate summary?<br>
<br></blockquote><div><br></div><div>I think that is a reasonable summary for the level that most people care about. It might be a bit pedantic, but what I'm aiming for is for us to be able to define the shared library set to correspond with our notion of component boundaries (follows public APIs), as that is what opens up the ability to optimize them in the future (BUILD_SHARED_LIBS is just a 1:1 add_library call -> shared library approach and leaks a lot of private boundaries). Also, it preserves the ability for executables to choose to link statically or dynamically, which is important for some things (and likely will remain so, especially when considering downstream).</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I would prefer for any large change like this that we do not add any net <br>
new configuration options (meaning if we add a new option we should <br>
remove an old one)to LLVM as we already have too many. Would this be <br>
able to replace BUILD_SHARED_LIBS=ON?<br></blockquote><div><br></div><div>Completely agree in the end state. I would like to converge on one configuration option that enables shared linking and then remove the others. I suspect that downstreams may want to customize things a bit more, but we should avoid adding those options to the extent possible in favor of seeing if we can make the default way workable before fragmenting.</div><div><br></div><div>Note that BUILD_SHARED_LIBS is a published way in the CMake ecosystem to tell a project to build in shared library mode. If we get this all fixed, we may still want to recognize when users set it and do the right thing (i.e. make it more of an alias). This viewpoint would argue for removing LLVM_BUILD_LLVM_DYLIB and just supporting BUILD_SHARED_LIBS (but with new behavior). Either way, we should keep the variants to a minimum.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
- Tom<br>
<br>
> *What I would need:*<br>
> <br>
> * Help, testing and expertise. I am reasonably confident in my<br>
> understanding of how to make shared libraries work and how to use<br>
> CMake, but the legacy in LLVM here is deep -- I likely pattern<br>
> matched some old features as no longer needed when they actually are<br>
> (I am not clear at all on how much of LLVM-Config is still relevant).<br>
> * Pointers to who the stakeholders are that I should be coordinating with.<br>
> <br>
> Comments?<br>
> <br>
> Thanks!<br>
> - Stella<br>
> <br>
> _______________________________________________<br>
> LLVM Developers mailing list<br>
> <a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
> <a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
> <br>
<br>
</blockquote></div></div>