peter.smith added inline comments.
================ Comment at: clang/docs/Multilib.rst:125 +``-fno-exceptions`` multilib variant need only contain C++ libraries. + +Stability ---------------- Although implicit in the mechanism, is it worth highlighting that layered multib.yaml authors will need to make sure that the includes and the libraries in the layer need to be complete enough to mask any incompatibilities? For example if in the `-fno-exceptions` case there exists a library `libX.a` that is affected by `-fno-exceptions` but is present in the "Core directory" but not the layered no-exceptions directory then the exceptions libX.a will be selected. /fp/libX.a (should have a noexcept variant in noexcept but multilib implementer gets it wrong!) /fp/libY.a /fp/lib/noexecpt/libY.a execeptions is perhaps not the best example here as including a file with exceptions when the intention is `-fno-exceptions` is not optimal, but it will work. If there is layering for floating point calling conventions then a mix could result in a broken program. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D143587/new/ https://reviews.llvm.org/D143587 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
