[llvm-bugs] [Bug 41251] New: llvm-config omits flags that are impactful to ABI

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=41251

            Bug ID: 41251
           Summary: llvm-config omits flags that are impactful to ABI
           Product: tools
           Version: trunk
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: llvm-config
          Assignee: unassignedbugs at nondot.org
          Reporter: mh+llvm at glandium.org
                CC: llvm-bugs at lists.llvm.org, sylvestre at debian.org

I got this interesting case where clang is built with -stdlib=libc++, and a
plugin is not (because as of https://reviews.llvm.org/D55391, -stdlib=libc++ is
not returned by llvm-config), where the plugin would fail to load because of
the missing symbol:
_ZN5clang12ast_matchers8internal15DynTypedMatcher17constructVariadicENS2_16VariadicOperatorENS_15ast_type_traits11ASTNodeKindESt6vectorIS2_SaIS2_EE
, while clang does have
_ZN5clang12ast_matchers8internal15DynTypedMatcher17constructVariadicENS2_16VariadicOperatorENS_15ast_type_traits11ASTNodeKindENSt3__16vectorIS2_NS6_9allocatorIS2_EEEE

As it turns out, std::vector is in a different namespace in libc++, so
-stdlib=libc++ makes a whole lot of a difference.

I wonder if there are other flags that are left out the same way since that
change.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20190327/c4953973/attachment.html>