[llvm-bugs] [Bug 32875] New: gcc attribute abi_tag not working correctly?

[via llvm-bugs]

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

            Bug ID: 32875
           Summary: gcc attribute abi_tag not working correctly?
           Product: clang
           Version: trunk
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: Frontend
          Assignee: unassignedclangbugs at nondot.org
          Reporter: jorgensen at kcg.com
                CC: llvm-bugs at lists.llvm.org

It seems the gcc abi::cxx11 tag compatibility isn't working right, at least not
with the gcc 6.3.0, don't know if that's expected or not. If you compile this:

#include <string>
#include <iostream>

int main()
{
   std::string msg = "hello world";
   std::ios_base::failure f(msg);
   return 0;
}

your compile goes like this:

#include <string>
#include <iostream>

int main()
{
   std::string msg = "hello world";
   std::ios_base::failure f(msg);
   return 0;
}

Here's clang(&gcc) info:

clang++ -v
clang version 5.0.0 (trunk 301891)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /home/jorgensen/bin/clangbuild
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8.5
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5.4.1
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6.3.0
Selected GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6.3.0
Candidate multilib: .;@m64
Selected multilib: .;@m64

I just built from trunk before filing this issue. 

FWIW if I look at the symbols in the std++ lib I see:

nm --dynamic /usr/lib/x86_64-linux-gnu/libstdc++.so.6 | c++filt | grep
'std::ios_base::failure'
000000000009fe00 T std::ios_base::failure::what() const
00000000000c1fb0 T std::ios_base::failure[abi:cxx11]::what() const
00000000000c27a0 T std::ios_base::failure[abi:cxx11]::cxx11(char const*,
std::error_code const&)
00000000000c20a0 T
std::ios_base::failure[abi:cxx11]::cxx11(std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > const&)
00000000000c2400 T
std::ios_base::failure[abi:cxx11]::cxx11(std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > const&, std::error_code const&)
00000000000c27a0 T std::ios_base::failure[abi:cxx11]::cxx11(char const*,
std::error_code const&)
00000000000c20a0 T
std::ios_base::failure[abi:cxx11]::cxx11(std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > const&)
00000000000c2400 T
std::ios_base::failure[abi:cxx11]::cxx11(std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > const&, std::error_code const&)
00000000000c1f90 T std::ios_base::failure[abi:cxx11]::~cxx11()
00000000000c1f70 T std::ios_base::failure[abi:cxx11]::~cxx11()
00000000000c1f70 T std::ios_base::failure[abi:cxx11]::~cxx11()
000000000009fec0 T std::ios_base::failure::failure(std::basic_string<char,
std::char_traits<char>, std::allocator<char> > const&)
000000000009fec0 T std::ios_base::failure::failure(std::basic_string<char,
std::char_traits<char>, std::allocator<char> > const&)
000000000009fea0 T std::ios_base::failure::~failure()
000000000009fe10 T std::ios_base::failure::~failure()
000000000009fe10 T std::ios_base::failure::~failure()
000000000037c388 V typeinfo for std::ios_base::failure[abi:cxx11]
000000000037a700 V typeinfo for std::ios_base::failure
0000000000140f30 V typeinfo name for std::ios_base::failure[abi:cxx11]
000000000013d490 V typeinfo name for std::ios_base::failure
000000000037c408 V vtable for std::ios_base::failure[abi:cxx11]
000000000037a718 V vtable for std::ios_base::failure

-- 
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/20170502/441fec03/attachment-0001.html>