File: libstdcxx_atomic_ns_hack.cpp

package info (click to toggle)
llvm-toolchain-9 1%3A9.0.1-16.1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 882,388 kB
  • sloc: cpp: 4,167,636; ansic: 714,256; asm: 457,610; python: 155,927; objc: 65,094; sh: 42,856; lisp: 26,908; perl: 7,786; pascal: 7,722; makefile: 6,881; ml: 5,581; awk: 3,648; cs: 2,027; xml: 888; javascript: 381; ruby: 156
file content (35 lines) | stat: -rw-r--r-- 891 bytes parent folder | download | duplicates (19)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
// RUN: %clang_cc1 -fsyntax-only -std=c++11 -verify %s

// libstdc++ 4.6.x contains a bug where it defines std::__atomic[0,1,2] as a
// non-inline namespace, then selects one of those namespaces and reopens it
// as inline, as a strange way of providing something like a using-directive.
// Clang has an egregious hack to work around the problem, by allowing a
// namespace to be converted from non-inline to inline in this one specific
// case.

#ifdef BE_THE_HEADER

#pragma clang system_header

namespace std {
  namespace __atomic0 {
    typedef int foobar;
  }
  namespace __atomic1 {
    typedef void foobar;
  }

  inline namespace __atomic0 {}
}

#else

#define BE_THE_HEADER
#include "libstdcxx_atomic_ns_hack.cpp"

std::foobar fb;

using T = void; // expected-note {{here}}
using T = std::foobar; // expected-error {{different types ('std::foobar' (aka 'int') vs 'void')}}

#endif