C++98 and C++03 are effectively aliases as far as Clang is concerned. As such, allowing both std=c++98 and std=c++03 as Lit parameters is just slightly confusing, but provides no value. It's similar to allowing both std=c++17 and std=c++1z, which we don't do. This was discovered because we had an internal bot that ran the test suite under both c++98 AND c++03 -- one of which is redundant. Differential Revision: https://reviews.llvm.org/D80926
32 lines
857 B
C++
32 lines
857 B
C++
//===----------------------------------------------------------------------===//
|
|
//
|
|
// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
|
|
// See https://llvm.org/LICENSE.txt for license information.
|
|
// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
|
|
//
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
// UNSUPPORTED: c++03, c++11
|
|
|
|
// shared_timed_mutex was introduced in macosx10.12
|
|
// UNSUPPORTED: with_system_cxx_lib=macosx10.11
|
|
// UNSUPPORTED: with_system_cxx_lib=macosx10.10
|
|
// UNSUPPORTED: with_system_cxx_lib=macosx10.9
|
|
|
|
// <shared_mutex>
|
|
|
|
// class shared_timed_mutex;
|
|
|
|
// shared_timed_mutex& operator=(const shared_timed_mutex&) = delete;
|
|
|
|
#include <shared_mutex>
|
|
|
|
int main(int, char**)
|
|
{
|
|
std::shared_timed_mutex m0;
|
|
std::shared_timed_mutex m1;
|
|
m1 = m0;
|
|
|
|
return 0;
|
|
}
|