On 06.11.2017 17:21, Steven Watanabe
via Boost-build wrote:
On 11/06/2017 03:03 PM, Stefan Seefeld via Boost-build wrote:
I just notice that bjam measures time (via `timestamp_current()`) on non-Windows
systems by simply calling `time()`, rather than something more precise such as
`gettimeofday()`. Do you know why ?
Historical reasons, probably. timestamp_current needs to be
be consistent with the code that reads the file timestamps,
which uses struct stat.m_time (which is a time_t). The code
was updated to get higher resolution on Windows, but not for
OK. I have switched to gettimeofday() in my fork, which makes timing
command performance much more meaningful. Looking into this I also
noticed a bug in the `timestamp_delta_seconds()` implementation
The factor should be 1e9 rather than 1e6 (it's nanoseconds, not
microseconds that get added to seconds).
...ich hab' noch einen Koffer in Berlin...