
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
29 lines
680 B
C++
29 lines
680 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
|
|
|
|
// <filesystem>
|
|
|
|
#include "filesystem_include.h"
|
|
|
|
using namespace fs;
|
|
|
|
struct ConvToPath {
|
|
operator fs::path() const {
|
|
return "";
|
|
}
|
|
};
|
|
|
|
int main(int, char**) {
|
|
ConvToPath LHS, RHS;
|
|
(void)(LHS / RHS); // expected-error {{invalid operands to binary expression}}
|
|
|
|
return 0;
|
|
}
|