[posix_time] ARM clock scaling issue
Hello, I am using the posix_time ptime interface to gauge clock times, universal time (Utc), and do date/time math, subtracting for durations type thing. What I am finding is that the accuracy seems to be fast. By how much I don't know, whether that's by a factor of what, or what not, I do not know. We are encountering this on an ARM platform. Has anyone else experience this? If so what can we do to workaround it? Assuming we stick with the Boost API to comprehend date/time, duration, our stopwatch abstraction, elapsed-timer, and so on. Thank you... Regards, Michael Powell
Meh... Before I go spinning my wheels or rewriting history here...
Looks like I might need to define:
BOOST_DATE_TIME_HAS_HIGH_PRECISION_CLOCK, and BOOST_HAS_GETTIMEOFDAY,
in order to realize a high-precision clock.
Thank you...
On Wed, Aug 28, 2013 at 3:57 PM, Michael Powell
Hello,
I am using the posix_time ptime interface to gauge clock times, universal time (Utc), and do date/time math, subtracting for durations type thing.
What I am finding is that the accuracy seems to be fast. By how much I don't know, whether that's by a factor of what, or what not, I do not know.
We are encountering this on an ARM platform. Has anyone else experience this? If so what can we do to workaround it?
Assuming we stick with the Boost API to comprehend date/time, duration, our stopwatch abstraction, elapsed-timer, and so on.
Thank you...
Regards,
Michael Powell
participants (1)
-
Michael Powell