about summary refs log tree commit diff
path: root/src/test/incremental/thinlto
diff options
context:
space:
mode:
authorkennytm <kennytm@gmail.com>2018-02-28 19:15:27 +0800
committerGitHub <noreply@github.com>2018-02-28 19:15:27 +0800
commitf933dd243ac4422660baecb9c2e3ac26522e59bd (patch)
tree0d8a1d498fad4e02a574883b725f58912a492768 /src/test/incremental/thinlto
parentddab91a5debadfda47c057117c8b498a31abaae7 (diff)
parent2985a1abfb48adeb848386377a8c6a3560c17910 (diff)
downloadrust-f933dd243ac4422660baecb9c2e3ac26522e59bd.tar.gz
rust-f933dd243ac4422660baecb9c2e3ac26522e59bd.zip
Rollup merge of #48266 - pietroalbini:report-compiler-flags-on-ice, r=michaelwoerister
Report non-standard compile flags on ICE

Some ICEs (such as the recent #48248) only happens when a non-standard compiler flag is provided to rustc, but users don't always report the used flags. This can slow down reproducing the issue, so this PR shows all the non-standard compiler flags in the ICE error message.

For example, the output of #48248 with this PR is:

```
error: internal compiler error: [...]

thread 'rustc' panicked at [...]
note: Run with `RUST_BACKTRACE=1` for a backtrace.

note: the compiler unexpectedly panicked. this is a bug.

note: we would appreciate a bug report: [...]

note: rustc 1.25.0-dev running on x86_64-unknown-linux-gnu

note: compiler flags: -C link-dead-code
```

### Open questions

* At the moment, only `-C` and `-Z` flags are shown by default, and all the ones provided by cargo in a standard build are ignored: I did this to only show the flags that probably caused the ICE, and to remove some noise from the message. This removed flags like `opt-level` and `debuginfo` though, could those be useful for reproducing ICEs?
Diffstat (limited to 'src/test/incremental/thinlto')
0 files changed, 0 insertions, 0 deletions