Uh oh!
There was an error while loading. Please reload this page.
Provide option for specifying the profiler runtime - #85284
Conversation
rust-highfive
commented
May 14, 2021
r? @jackh726 (rust-highfive has picked a reviewer for you, use r? to override) |
Uh oh!
There was an error while loading. Please reload this page.
Currently, if `-Zinstrument-coverage` is enabled, the target is linked against the `library/profiler_builtins` crate (which pulls in LLVM's compiler-rt runtime). This option enables backends to specify an alternative runtime crate for handling injected instrumentation calls.
5e5cb17 to
93c6362Compare
jackh726
left a comment
There was a problem hiding this comment.
So, is there currently any work being held up elsewhere by this? I.e. is there another profiler runtime ready?
I'm also not sure if this deserves an MCP. I'm not sure how used this option is?
There might be someone better to review this then me (someone more familiar in this area). That being said, the code changes here look mostly fine (modulo one nit). Are there any tests that can be added here?
Uh oh!
There was an error while loading. Please reload this page.
jackh726
commented
Jun 1, 2021
@eggyal do you know someone who might be a better reviewer? I'm basically okay approving this, if
|
eggyal
commented
Jun 1, 2021
I have an alternative profiler runtime for an under-development incremental test runner that uses cg_clif, but it's not ready no. @bjorn3 do you have r+ privileges? Would you be an appropriate reviewer for this? Else perhaps @tmandry or @wesleywiser given that the profiler runtime is part of the coverage instrumentation that I think they oversaw? |
wesleywiser
commented
Jun 1, 2021
This seems fine to me but let's cc @Amanieu who added |
I added that flag for minicov which provides a Since the profiler runtime is provided by the crate, it just needs rustc/LLVM to emit the profiling instrumentation without injecting a profiling runtime. |
eggyal
commented
Jun 17, 2021
@rustbot label: +S-waiting-on-review -S-waiting-on-author |
jackh726
commented
Jun 17, 2021
bors
commented
Jun 17, 2021
📌 Commit 872839e has been approved by |
bors
commented
Jun 18, 2021
bors
commented
Jun 18, 2021
☀️ Test successful - checks-actions |
This was removed by rust-lang#85284 in favor of -Zprofiler-runtime=<name>. However the suggested -Zprofiler-runtime=None doesn't work because "None" is treated as a crate name.
…h726 Add back -Zno-profiler-runtime This was removed by rust-lang#85284 in favor of `-Zprofiler-runtime=<name>`.However the suggested `-Zprofiler-runtime=None` doesn't work because`None` is treated as a crate name.
…h726 Add back -Zno-profiler-runtime This was removed by rust-lang#85284 in favor of `-Zprofiler-runtime=<name>`.However the suggested `-Zprofiler-runtime=None` doesn't work because`None` is treated as a crate name.
Currently, if
-Zinstrument-coverageis enabled, the target is linkedagainst the
library/profiler_builtinscrate (which pulls in LLVM'scompiler-rt runtime).
This option enables backends to specify an alternative runtime crate for
handling injected instrumentation calls.