diff options
author | Zbigniew Sarbinowski <zibi@ca.ibm.com> | 2021-02-12 18:36:15 +0000 |
---|---|---|
committer | Zbigniew Sarbinowski <zibi@ca.ibm.com> | 2021-02-12 18:39:48 +0000 |
commit | cb2d2ae56ae3f0554c40c2d7f231ca5058e4d50c (patch) | |
tree | a2e4ceb3f9115c3de1ab8ae0d7ef0474a9e4fae5 /llvm/lib/DebugInfo/Symbolize/SymbolizableObjectFile.cpp | |
parent | 875f0cbcc6d5ff9b36e667911e96fcdf6afc698e (diff) | |
download | llvm-cb2d2ae56ae3f0554c40c2d7f231ca5058e4d50c.zip llvm-cb2d2ae56ae3f0554c40c2d7f231ca5058e4d50c.tar.gz llvm-cb2d2ae56ae3f0554c40c2d7f231ca5058e4d50c.tar.bz2 |
[SystemZ][ZOS] Provide CLOCK_MONOTONIC alternative
We need CLOCK_MONOTONIC equivalent implementation for z/OS within libc++. The default implementation is asserting.
On z/OS the lack of 'clock_gettime()' and 'time_point()' force us to look for alternatives.
The current proposal is to use `gettimeofday()` for CLOCK_MONOTONIC which is also used in CLOCK_REALTIME. This will allow us to skip the assertion with compromised CLOCK_MONOTONIC implementation which will not guarantee to never go back in time because it will use `gettimeofday()` but only when it's set.
Is this a good compromise for platforms which does not support monotonic clock?
Hopefully this will spark the discussion and agreement how to proceed in this situation.
Reviewed By: #libc, ldionne, hubert.reinterpretcast
Differential Revision: https://reviews.llvm.org/D93542
Diffstat (limited to 'llvm/lib/DebugInfo/Symbolize/SymbolizableObjectFile.cpp')
0 files changed, 0 insertions, 0 deletions