diff options
| author | Yuki Okushi <huyuumi.dev@gmail.com> | 2020-10-17 05:36:52 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-10-17 05:36:52 +0900 |
| commit | d334059696e57b882903d9d852d3e64ae887f5ec (patch) | |
| tree | 5eda673ae3cb0ec8a9b0319d3a48b52cd699ec19 /compiler/rustc_codegen_llvm/src | |
| parent | b4282b37f167dfec0e383fa1c9dc05b073621aae (diff) | |
| parent | 8436cfe71db9a3f0c6b6d8f44fd18b4d6612627a (diff) | |
| download | rust-d334059696e57b882903d9d852d3e64ae887f5ec.tar.gz rust-d334059696e57b882903d9d852d3e64ae887f5ec.zip | |
Rollup merge of #77992 - nagisa:thaw-coverage-instrumentation, r=wesleywiser
instrument-coverage: try our best to not ICE instrument-coverage was ICEing for me on some code, in particular code that had devirtualized paths from standard library. Instrument coverage probably has no bussiness dictating which paths are valid and which aren't so just feed it everything and whatever and let tooling deal with other stuff. For example, with this commit we can generate coverage hitpoints for these interesting paths: * `/rustc/.../library/core/lib.rs` – non-devirtualized path for libcore * `/home/.../src/library/core/lib.rs` – devirtualized version of above * `<inline asm>`, `<anon>` and many similar synthetic paths Even if those paths somehow get to the instrumentation pass, I'd much rather get hits for these weird paths and hope some of them work (as would be the case for devirtualized path to libcore), rather than have compilation fail entirely.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions