diff options
| author | Zalathar <Zalathar@users.noreply.github.com> | 2024-06-01 21:35:43 +1000 |
|---|---|---|
| committer | Zalathar <Zalathar@users.noreply.github.com> | 2024-06-19 20:41:34 +1000 |
| commit | fd4fe7d129cac2b7a0668847117775ee23031771 (patch) | |
| tree | 14db5333ade7ca080b12da0fc10f39a0ebe44f96 /src/doc | |
| parent | 3c0f019b3c56c1a0e6e0cbed6f8a8b0b245e5665 (diff) | |
| download | rust-fd4fe7d129cac2b7a0668847117775ee23031771.tar.gz rust-fd4fe7d129cac2b7a0668847117775ee23031771.zip | |
Remove `src/tools/rust-demangler`
Diffstat (limited to 'src/doc')
| -rw-r--r-- | src/doc/rustc/src/instrument-coverage.md | 8 |
1 files changed, 1 insertions, 7 deletions
diff --git a/src/doc/rustc/src/instrument-coverage.md b/src/doc/rustc/src/instrument-coverage.md index 32dc992c42f..ed091d8fc57 100644 --- a/src/doc/rustc/src/instrument-coverage.md +++ b/src/doc/rustc/src/instrument-coverage.md @@ -49,12 +49,6 @@ One option for a Rust demangler is [`rustfilt`], which can be installed with: cargo install rustfilt ``` -Another option, if you are building from the Rust compiler source distribution, is to use the `rust-demangler` tool included in the Rust source distribution, which can be built with: - -```shell -$ ./x.py build rust-demangler -``` - [`rustfilt`]: https://crates.io/crates/rustfilt ## Compiling with coverage enabled @@ -164,7 +158,7 @@ $ llvm-cov show -Xdemangler=rustfilt target/debug/examples/formatjson5 \ Some of the more notable options in this example include: -- `--Xdemangler=rustfilt` - the command name or path used to demangle Rust symbols (`rustfilt` in the example, but this could also be a path to the `rust-demangler` tool) +- `--Xdemangler=rustfilt` - the command name or path used to demangle Rust symbols (`rustfilt` in the example) - `target/debug/examples/formatjson5` - the instrumented binary (from which to extract the coverage map) - `--instr-profile=<path-to-file>.profdata` - the location of the `.profdata` file created by `llvm-profdata merge` (from the `.profraw` file generated by the instrumented binary) - `--name=<exact-function-name>` - to show coverage for a specific function (or, consider using another filter option, such as `--name-regex=<pattern>`) |