chrono: correct the units for the epoch bias
As pointed out by Howard, this is actually 134774 days (* 24 * 3600),
and therefore seconds, not 100ns units. Adjust the units to reflect
reality.
llvm-svn: 290824
Cr-Mirrored-From: sso://chromium.googlesource.com/_direct/external/github.com/llvm/llvm-project
Cr-Mirrored-Commit: d1c346a43ba44f1e5ad2d0d0d9b94e835d221ae6
diff --git a/src/chrono.cpp b/src/chrono.cpp
index b9d6bf9..28cdb9d 100644
--- a/src/chrono.cpp
+++ b/src/chrono.cpp
@@ -53,8 +53,7 @@
nanoseconds::period>>;
// The Windows epoch is Jan 1 1601, the Unix epoch Jan 1 1970.
- static _LIBCPP_CONSTEXPR const filetime_duration
- nt_to_unix_epoch{11644473600};
+ static _LIBCPP_CONSTEXPR const seconds nt_to_unix_epoch{11644473600};
FILETIME ft;
#if _WIN32_WINNT >= _WIN32_WINNT_WIN8