summaryrefslogtreecommitdiff
path: root/lldb/test/API/functionalities/progress_reporting/clang_modules
AgeCommit message (Collapse)Author
2024-04-26[lldb][sbapi] Fix API break in SBDebugger broadcast bits (#90261)Chelsea Cassanova
https://github.com/llvm/llvm-project/pull/87409 removed the broadcast bits from SBDebugger and placed them in `lldb-enumerations.h`. This is API-breaking so this commits places the enum back into `SBDebugger.h` and references the bits from `lldb-enumerations.h`. rdar://127128536
2024-04-11Reland "[lldb][sbdebugger] Move SBDebugger Broadcast bit enum into ll… ↵Chelsea Cassanova
(#88331) …db-enumerations.h" (#88324)" This reverts commit 9f6d08f2566a26144ea1753f80aebb1f2ecfdc63. This broke the build because of a usage of one of the original SBDebugger broadcast bits that wasn't updated in the original commit.
2024-04-10Revert "[lldb][sbdebugger] Move SBDebugger Broadcast bit enum into ↵Chelsea Cassanova
lldb-enumerations.h" (#88324) Reverts llvm/llvm-project#87409 due a missed update to the broadcast bit causing a build failure on the x86_64 Debian buildbot.
2024-04-10[lldb][sbdebugger] Move SBDebugger Broadcast bit enum into ↵Chelsea Cassanova
lldb-enumerations.h (#87409) When the `eBroadcastBitProgressCategory` bit was originally added to Debugger.h and SBDebugger.h, each corresponding bit was added in order of the other bits that were previously there. Since `Debugger.h` has an enum bit that `SBDebugger.h` does not, this meant that their offsets did not match. Instead of trying to keep the bit offsets in sync between the two, it's preferable to just move SBDebugger's enum into the main enumerations header and use the bits from there. This also requires that API tests using the bits from SBDebugger update their usage.
2023-03-30[lldb] Use one Progress event per root module buildDave Lee
Following the work done by @jdevlieghere in D143690, this changes how Clang module build events are emitted. Instead of one Progress event per module being built, a single Progress event is used to encompass all modules, and each module build is sent as an `Increment` update. Differential Revision: https://reviews.llvm.org/D147248
2022-12-16[lldb] Report clang module build remarksDave Lee
Update the Clang diagnostic consumer (in ClangModulesDeclVendor) to report progress on Clang module builds, as both progress events and expression logs. Module build remarks are enabled by with clang's `-Rmodule-build` flag. With this change, command line users of lldb will see progress events showing which modules are being built, and - by how long they stay on screen - how much time it takes to build them. IDEs that show progress events can show these updates if desired. This does not show module-import remarks, although that may be added as a future change. Differential Revision: https://reviews.llvm.org/D140056