As suggested by Ivan Maidanski:
The clock_gettime(CLOCK_MONOTONIC) function may fail on some machines (even
if _POSIX_MONOTONIC_CLOCK has been defined during compilation), so it's
better to silently fall-back to gettimeofday() in that case.
Cc: Andrew Hughes <gnu_and...@members.fsf.org>
Cc: Ivan Maidanski <iv...@mail.ru>
Signed-off-by: Pekka Enberg <penb...@kernel.org>
---
native/jni/java-lang/java_lang_VMSystem.c | 4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/native/jni/java-lang/java_lang_VMSystem.c
b/native/jni/java-lang/java_lang_VMSystem.c
index 44f789f..047c2b3 100644
--- a/native/jni/java-lang/java_lang_VMSystem.c
+++ b/native/jni/java-lang/java_lang_VMSystem.c
@@ -146,9 +146,7 @@ Java_java_lang_VMSystem_nanoTime
struct timespec tp;
if (clock_gettime (CLOCK_MONOTONIC, &tp) == -1) {
- char error[64];
- snprintf(error, 64, "clock_gettime call failed: %s.", strerror(errno));
- (*env)->FatalError (env, error);
+ return currentTimeMicros(env) * (jlong)1000;
}
result = (jlong) tp.tv_sec;
--
1.7.0.4
