f8764e30d5
The tests for libc++ specify -target on the command-line to the compiler, but this is problematic for a few reasons. Firstly, the -target option isn't supported on Apple platforms. Parts of the triple get dropped and ignored. Instead, software should be compiled with a combination of the -arch and -m<name>-version-min options. Secondly, the generic "darwin" target references a kernel version instead of a platform version. Each platform has its own independent versions (with different versions of libc++.1.dylib), independent of the version of the Darwin kernel. This commit adds support to the LIT infrastructure for testing against Apple platforms using -arch and -platform options. If the host is not on OS X, or the compiler type is not clang or apple-clang, then this commit has NFC. If the host is on OS X and --param=target_triple=... is specified, then a warning is emitted to use arch and platform instead. Besides the warning, there's NFC. If the host is on OS X and *no* target-triple is specified, then use the new deployment target logic. This uses two new lit parameters, --param=arch=<arch> and --param=platform=<platform>. <platform> has the form <name>[<version>]. By default, arch is auto-detected from clang -dumpmachine, and platform is "macosx". If the platform doesn't have a version: For "macosx", the version is auto-detected from the host system using sw_vers. This may give a different version than the SDK, since new SDKs can be installed on older hosts. Otherwise, the version is auto-detected from the SDK version using xcrun --show-sdk-path. -arch <arch> -m<name>-version-min=<version> is added to the compiler flags. The target triple is computed as <arch>-apple-<platform>. It is *not* passed to clang, but it is available for XFAIL and UNSUPPORTED (as is with_system_cxx_lib=<target>). For convenience, apple-darwin and <arch>-apple-darwin are added to the set of available features. There were a number of tests marked to XFAIL on x86_64-apple-darwin11 and x86_64-apple-darwin12. I updated these to x86_64-apple-macosx10.7 and x86_64-apple-macosx10.8. llvm-svn: 297798
53 lines
1.8 KiB
C++
53 lines
1.8 KiB
C++
//===----------------------------------------------------------------------===//
|
|
//
|
|
// The LLVM Compiler Infrastructure
|
|
//
|
|
// This file is dual licensed under the MIT and the University of Illinois Open
|
|
// Source Licenses. See LICENSE.TXT for details.
|
|
//
|
|
//===----------------------------------------------------------------------===//
|
|
//
|
|
// UNSUPPORTED: libcpp-has-no-threads
|
|
|
|
// LWG 2056 changed the values of future_errc, so if we're using new headers
|
|
// with an old library we'll get incorrect messages.
|
|
//
|
|
// XFAIL: with_system_cxx_lib=x86_64-apple-macosx10.7
|
|
// XFAIL: with_system_cxx_lib=x86_64-apple-macosx10.8
|
|
// XFAIL: with_system_cxx_lib=x86_64-apple-darwin13
|
|
|
|
// <future>
|
|
|
|
// class future_error
|
|
|
|
// const char* what() const throw();
|
|
|
|
#include <future>
|
|
#include <cstring>
|
|
#include <cassert>
|
|
|
|
#include "test_macros.h"
|
|
|
|
int main()
|
|
{
|
|
{
|
|
std::future_error f(std::make_error_code(std::future_errc::broken_promise));
|
|
LIBCPP_ASSERT(std::strcmp(f.what(), "The associated promise has been destructed prior "
|
|
"to the associated state becoming ready.") == 0);
|
|
}
|
|
{
|
|
std::future_error f(std::make_error_code(std::future_errc::future_already_retrieved));
|
|
LIBCPP_ASSERT(std::strcmp(f.what(), "The future has already been retrieved from "
|
|
"the promise or packaged_task.") == 0);
|
|
}
|
|
{
|
|
std::future_error f(std::make_error_code(std::future_errc::promise_already_satisfied));
|
|
LIBCPP_ASSERT(std::strcmp(f.what(), "The state of the promise has already been set.") == 0);
|
|
}
|
|
{
|
|
std::future_error f(std::make_error_code(std::future_errc::no_state));
|
|
LIBCPP_ASSERT(std::strcmp(f.what(), "Operation not permitted on an object without "
|
|
"an associated state.") == 0);
|
|
}
|
|
}
|