History log of /system/core/libutils/SystemClock.cpp
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
9b828adfad09200f3f1bd3602187fe3dd5335774 30-Jul-2015 Elliott Hughes <enh@google.com> Use __ANDROID__ instead of HAVE_ANDROID_OS.

Change-Id: I9967f3fd758c2a5b40be5b60ae72be7e2fb75136
/system/core/libutils/SystemClock.cpp
6ed68cc412752e4c78755df9a1516e610ec66fa8 30-Jun-2015 Elliott Hughes <enh@google.com> Consistently use strerror in libutils.

It's easier for people to debug, and side-steps the problem that errno
values differ between architectures.

Bug: http://b/17458391
Change-Id: I1db9b2cbb653839d3936b91e37e5cff02671318a
/system/core/libutils/SystemClock.cpp
22a40e6a7a8e313cea310503fb42c4b66f535843 04-Dec-2014 Elliott Hughes <enh@google.com> Use __arm__ instead of ARCH_ARM.

Change-Id: I777da5757f01d8328d5475e654d56d81dc802655
/system/core/libutils/SystemClock.cpp
5bed8036644f552210a7cfcbed2d6d20cf2981b0 30-Apr-2014 Mark Salyzyn <salyzyn@google.com> libutils: turn on -Werror

- Deal with some -Wunused issues
- Override PRI macros (windows)
- Revert use of PRI macros on off64_t (linux)
- Deal with a gnu++11 complaince issue

Change-Id: Ie66751293bd84477a5a6dfd8a57e700a16e36964
/system/core/libutils/SystemClock.cpp
64289760a2df9409d8f4fa5becb4a49f0acb20a5 17-Dec-2013 Greg Hackmann <ghackmann@google.com> SystemClock: use clock_gettime() on devices without /dev/alarm

On devices with an up-to-date kernel, the back-in-time bug affecting
clock_gettime() has been fixed and it can safely be used as an
alternative to the ANDROID_ALARM_GET_TIME ioctl. To ensure consistent
behavior on existing devices, make clock_gettime() a fallback for when
the alarm driver isn't available.

Change-Id: I384af5e7ec9e73e0bad4b6b0f987a8ea4583cba6
Signed-off-by: Greg Hackmann <ghackmann@google.com>
/system/core/libutils/SystemClock.cpp
5cd118178e87c4a6590dc8d8446effa5d5193a9f 24-Sep-2013 Ben Cheng <bccheng@google.com> Disable timestamp logging.

The kernel problem has been fixed long time ago and the ad-hoc logging
mechanism is not thread safe and can flood the log with spurious
messages.

BUG: 10899829
Change-Id: I63278db51295e744eed3e47dc8d4cfe621c0d8f7
/system/core/libutils/SystemClock.cpp
d98e07fdf9c338589f263c47ce5c844ed43efad5 02-Aug-2013 Alex Ray <aray@google.com> move libs/utils to libutils

Change-Id: I6cf4268599460791414882f91eeb88a992fbd29d
/system/core/libutils/SystemClock.cpp