Bug ID: 37051
Summary: Provide a way to lock the current global XRay state
Currently, with the XRay API functions, it's easy to run into a situation where
a currently installed implementation can be unceremoniously uninstalled. We
should provide a stronger protocol for when we're attempting to select a new
mode, and deprecate specific API functions deemed too dangerous to use.
The protocol should include locking the global state, to not allow for
inadvertently interfering with a currently-installed mode.
You are receiving this mail because:
You are on the CC list for the bug.
llvm-bugs mailing list