diff options
| author | Guillaume Gomez <guillaume1.gomez@gmail.com> | 2018-01-25 15:52:13 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-01-25 15:52:13 +0100 |
| commit | bbdc5b9637db7d63f1754cef060bad6542b4c790 (patch) | |
| tree | 30db9fd07a18fd8681d595e63dc5fcb7d52f4595 /src/rustllvm/RustWrapper.cpp | |
| parent | 83603b8294861c54ed89809f9e3b12dd77367a9f (diff) | |
| parent | 5de8e040d2ed8f3d9da79a4f12b9ece51c352f2e (diff) | |
| download | rust-bbdc5b9637db7d63f1754cef060bad6542b4c790.tar.gz rust-bbdc5b9637db7d63f1754cef060bad6542b4c790.zip | |
Rollup merge of #47679 - etaoins:remove-redundant-backtrace-hint, r=estebank
Remove broken redundant backtrace hint When the compiler driver panics it attempts to show a hint about using `RUST_BACKTRACE`. However, the logic is currently reversed to the hint is only shown if `RUST_BACKTRACE` is **already** set: ```shell > RUST_BACKTRACE=1 rustc /dev/null --crate-type proc-macro error: internal compiler error: unexpected panic ... note: run with `RUST_BACKTRACE=1` for a backtrace thread 'rustc' panicked at 'attempt to subtract with overflow', librustc_errors/emitter.rs:287:49 note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace. > RUST_BACKTRACE=0 rustc /dev/null --crate-type proc-macro error: internal compiler error: unexpected panic ... thread 'rustc' panicked at 'attempt to subtract with overflow', librustc_errors/emitter.rs:287:49 note: Run with `RUST_BACKTRACE=1` for a backtrace. ``` As the `panic` itself already has a working `RUST_BACKTRACE` hint just remove the broken duplicate hint entirely.
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions
