No bug: Fix comment in TimeStamp_posix.cpp. DONTBUILD
authorJustin Lebar <justin.lebar@gmail.com>
Sat, 20 Oct 2012 11:12:20 -0400
changeset 111017 1e537983e72efe1f5047e28e41ac64b36907b428
parent 111003 5d03feda23009d5a79a1ed880a6ff20af57dbf2b
child 111018 1c4ecfb93f84671095ad3e0acb9044a2c5d88389
push id93
push usernmatsakis@mozilla.com
push dateWed, 31 Oct 2012 21:26:57 +0000
milestone19.0a1
No bug: Fix comment in TimeStamp_posix.cpp. DONTBUILD
xpcom/ds/TimeStamp_posix.cpp
--- a/xpcom/ds/TimeStamp_posix.cpp
+++ b/xpcom/ds/TimeStamp_posix.cpp
@@ -33,17 +33,17 @@ TimespecToNs(const struct timespec& ts)
   uint64_t baseNs = uint64_t(ts.tv_sec) * kNsPerSec;
   return baseNs + uint64_t(ts.tv_nsec);
 }
 
 static uint64_t
 ClockTimeNs()
 {
   struct timespec ts;
-  // this can't fail: we know &ts is valid, and TimeStamp::Init()
+  // this can't fail: we know &ts is valid, and TimeStamp::Startup()
   // checks that CLOCK_MONOTONIC is supported (and aborts if not)
   clock_gettime(CLOCK_MONOTONIC, &ts);
 
   // tv_sec is defined to be relative to an arbitrary point in time,
   // but it would be madness for that point in time to be earlier than
   // the Epoch.  So we can safely assume that even if time_t is 32
   // bits, tv_sec won't overflow while the browser is open.  Revisit
   // this argument if we're still building with 32-bit time_t around