diff options
| author | bors <bors@rust-lang.org> | 2018-10-28 18:49:46 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2018-10-28 18:49:46 +0000 |
| commit | 96064eb61dc703c289fae61bdf90593d3e7b2449 (patch) | |
| tree | 6c3428593dbec23a6ccf36984d478f154c17e6cb /src/rustllvm/RustWrapper.cpp | |
| parent | d492c6792c4fa24fb542bf457667f45b55b7c093 (diff) | |
| parent | 5903fdb28184d465c01cd6247d0e8ce0c4128211 (diff) | |
| download | rust-96064eb61dc703c289fae61bdf90593d3e7b2449.tar.gz rust-96064eb61dc703c289fae61bdf90593d3e7b2449.zip | |
Auto merge of #54487 - RalfJung:ctfe-backtrace, r=oli-obk
Delayed CTFE backtraces This renames the env var that controls CTFE backtraces from `MIRI_BACKTRACE` to `RUST_CTFE_BACKTRACE` so that we can use `MIRI_BACKTRACE` in the miri tool to only show backtraces of the main miri execution. It also makes `RUST_CTFE_BACKTRACE` only show backtraces that actually get rendered as errors, instead of showing them eagerly when the `Err` happens. The current behavior is near useless in miri because it shows about one gazillion backtraces for errors that we later catch and do not care about. However, @oli-obk likes the current behavior for rustc CTFE work so it is still available via `RUST_CTFE_BACKTRACE=immediate`. NOTE: This is based on top of https://github.com/rust-lang/rust/pull/53821. Only [the last three commits](https://github.com/oli-obk/rust/compare/sanity_query...RalfJung:ctfe-backtrace) are new. Fixes https://github.com/rust-lang/rust/issues/53355
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions
