
This commit reverts 5aaefa51 (and also partly 7f285f48e77 and b6d75682f9, which were related to the original commit). As landed, 5aaefa51 had unintended consequences on some downstream bots and didn't have proper coverage upstream due to a few subtle things. Implementing this is something we should do in libc++, however we'll first need to address a few issues listed in https://reviews.llvm.org/D106124#3349710. Differential Revision: https://reviews.llvm.org/D120683
45 lines
1.2 KiB
C++
45 lines
1.2 KiB
C++
// -*- 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
|
|
//
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
#ifndef _LIBCPP___CHRONO_STEADY_CLOCK_H
|
|
#define _LIBCPP___CHRONO_STEADY_CLOCK_H
|
|
|
|
#include <__chrono/duration.h>
|
|
#include <__chrono/time_point.h>
|
|
#include <__config>
|
|
|
|
#if !defined(_LIBCPP_HAS_NO_PRAGMA_SYSTEM_HEADER)
|
|
# pragma GCC system_header
|
|
#endif
|
|
|
|
_LIBCPP_BEGIN_NAMESPACE_STD
|
|
|
|
namespace chrono
|
|
{
|
|
|
|
#ifndef _LIBCPP_HAS_NO_MONOTONIC_CLOCK
|
|
class _LIBCPP_TYPE_VIS steady_clock
|
|
{
|
|
public:
|
|
typedef nanoseconds duration;
|
|
typedef duration::rep rep;
|
|
typedef duration::period period;
|
|
typedef chrono::time_point<steady_clock, duration> time_point;
|
|
static _LIBCPP_CONSTEXPR_AFTER_CXX11 const bool is_steady = true;
|
|
|
|
static time_point now() _NOEXCEPT;
|
|
};
|
|
#endif
|
|
|
|
} // namespace chrono
|
|
|
|
_LIBCPP_END_NAMESPACE_STD
|
|
|
|
#endif // _LIBCPP___CHRONO_STEADY_CLOCK_H
|