[Lldb-commits] [PATCH] D117474: [lldb] Make StatsDuration thread-safe

2022-01-19 Thread Pavel Labath via Phabricator via lldb-commits
This revision was automatically updated to reflect the committed changes. Closed by commit rG4f89157b9d73: [lldb] Make StatsDuration thread-safe (authored by labath). Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D117474/new/ https://reviews.llvm.org

[Lldb-commits] [PATCH] D117474: [lldb] Make StatsDuration thread-safe

2022-01-19 Thread Pavel Labath via Phabricator via lldb-commits
labath added a comment. The precision is now limited to microseconds (arbitrary choice that I though should be sufficient) whereas previously it was... floating. There are no changes besides that. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D1174

[Lldb-commits] [PATCH] D117474: [lldb] Make StatsDuration thread-safe

2022-01-18 Thread Greg Clayton via Phabricator via lldb-commits
clayborg accepted this revision. clayborg added a comment. This revision is now accepted and ready to land. Thanks for finding a solution. I tried originally doing a std::atomic but those are not supported. As long as you have verified that storing at a uint64_t reports the same kinds of duratio

[Lldb-commits] [PATCH] D117474: [lldb] Make StatsDuration thread-safe

2022-01-17 Thread Pavel Labath via Phabricator via lldb-commits
labath created this revision. labath added a reviewer: clayborg. Herald added a subscriber: arphaman. labath requested review of this revision. Herald added a project: LLDB. std::chrono::duration types are not thread-safe, and they cannot be concurrently updated from multiple threads. Currently, w