Really do make sure that last_write_time.pass.cpp still works with old clang

I *did* try to check that such kind of an issue was not introduced
by the rL315874, but clearly i failed to finish verification.

git-svn-id: https://llvm.org/svn/llvm-project/libcxx/trunk@315876 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Roman Lebedev
2017-10-15 20:46:12 +00:00
parent 0fdc4c9c6b
commit 4b05db4286

View File

@@ -89,9 +89,11 @@ bool TestSupportsNegativeTimes() {
}
// In some configurations, the comparison is tautological and the test is valid.
// We disable the warning so that we can actually test it regardless.
// We disable the warning so that we can actually test it regardless. Also, that
// diagnostic is pretty new, so also don't fail if old clang does not support it
#if defined(__clang__)
#pragma clang diagnostic push
#pragma clang diagnostic ignored "-Wunknown-warning-option"
#pragma clang diagnostic ignored "-Wtautological-constant-compare"
#endif
@@ -123,9 +125,11 @@ static const bool SupportsMaxTime = TestSupportsMaxTime();
} // end namespace
// In some configurations, the comparison is tautological and the test is valid.
// We disable the warning so that we can actually test it regardless.
// We disable the warning so that we can actually test it regardless. Also, that
// diagnostic is pretty new, so also don't fail if old clang does not support it
#if defined(__clang__)
#pragma clang diagnostic push
#pragma clang diagnostic ignored "-Wunknown-warning-option"
#pragma clang diagnostic ignored "-Wtautological-constant-compare"
#endif