On Tue, Mar 22, 2016 at 6:03 PM, Rebecca N. Palmer <rebecca_pal...@zoho.com> wrote: >> The user then compiled with Clang and caught a link error. > > clang can't handle abi tags (i.e. can't link to new-ABI code even if you > aren't trying to mix it with old-ABI code): > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797917 > https://llvm.org/bugs/show_bug.cgi?id=23529
Yes, correct. That's why we are asking that -Wabi-tag be enabled for GCC and Clang, similar to the way other options are pushed/enabled, like _FORTIFY_SOURCES (unless the user specifies -Wno-abi-tag). In our case, we are a library (Crypto++, https://www.cryptopp.com/), and we don't control how the library is compiled by a distro or how users compile their programs. A distro compiling the library is always OK; its the user and their choices that are creating the issues. The -Wabi-tag warning will serve to alert the user they've wandered into a problem area based on their choices. Jeff
