rust/tests/ui/consts/const-eval/unwind-abort.stderr

error[E0080]: evaluation of constant value failed
  --> $DIR/unwind-abort.rs:4:5
   |
LL |     panic!()
   |     ^^^^^^^^ the evaluated program panicked at 'explicit panic', $DIR/unwind-abort.rs:4:5
   |
note: inside `foo`
  --> $DIR/unwind-abort.rs:4:5
   |
LL |     panic!()
   |     ^^^^^^^^
note: inside `_`
  --> $DIR/unwind-abort.rs:7:15
   |
LL | const _: () = foo();
   |               ^^^^^
   = note: this error originates in the macro `$crate::panic::panic_2015` which comes from the expansion of the macro `panic` (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0080`.
Use better error message for hard errors in CTFE Currently the same message is used for hard errors and soft errors. This makes hard errors use a message that indicates the reality of the situation correctly, since usage of the constant is never allowed when there was a hard error evaluating it. 2021-06-15 19:16:10 -04:00			`error[E0080]: evaluation of constant value failed`
rustc: Fill out remaining parts of C-unwind ABI This commit intends to fill out some of the remaining pieces of the C-unwind ABI. This has a number of other changes with it though to move this design space forward a bit. Notably contained within here is: * On `panic=unwind`, the `extern "C"` ABI is now considered as "may unwind". This fixes a longstanding soundness issue where if you `panic!()` in an `extern "C"` function defined in Rust that's actually UB because the LLVM representation for the function has the `nounwind` attribute, but then you unwind. * Whether or not a function unwinds now mainly considers the ABI of the function instead of first checking the panic strategy. This fixes a miscompile of `extern "C-unwind"` with `panic=abort` because that ABI can still unwind. * The aborting stub for non-unwinding ABIs with `panic=unwind` has been reimplemented. Previously this was done as a small tweak during MIR generation, but this has been moved to a separate and dedicated MIR pass. This new pass will, for appropriate functions and function calls, insert a `cleanup` landing pad for any function call that may unwind within a function that is itself not allowed to unwind. Note that this subtly changes some behavior from before where previously on an unwind which was caught-to-abort it would run active destructors in the function, and now it simply immediately aborts the process. * The `#[unwind]` attribute has been removed and all users in tests and such are now using `C-unwind` and `#![feature(c_unwind)]`. I think this is largely the last piece of the RFC to implement. Unfortunately I believe this is still not stabilizable as-is because activating the feature gate changes the behavior of the existing `extern "C"` ABI in a way that has no replacement. My thinking for how to enable this is that we add support for the `C-unwind` ABI on stable Rust first, and then after it hits stable we change the behavior of the `C` ABI. That way anyone straddling stable/beta/nightly can switch to `C-unwind` safely. 2021-06-08 11:23:58 -07:00			`--> $DIR/unwind-abort.rs:4:5`
Ensure that the const-eval engine handles `#[unwind(aborts)]` 2020-10-03 15:09:43 -07:00			`\|`
Change CTFE backtraces to use `note` instead of `label` to preserve their order labels are reordered within the file in which they are reported, which can mess up the stack trace 2022-11-29 13:10:42 +00:00			`LL \| panic!()`
			`\| ^^^^^^^^ the evaluated program panicked at 'explicit panic', $DIR/unwind-abort.rs:4:5`
			`\|`
			note: inside `foo`
			`--> $DIR/unwind-abort.rs:4:5`
			`\|`
Ensure that the const-eval engine handles `#[unwind(aborts)]` 2020-10-03 15:09:43 -07:00			`LL \| panic!()`
add comment and bless some tests 2020-12-02 17:19:11 +05:30			`\| ^^^^^^^^`
Change CTFE backtraces to use `note` instead of `label` to preserve their order labels are reordered within the file in which they are reported, which can mess up the stack trace 2022-11-29 13:10:42 +00:00			note: inside `_`
			`--> $DIR/unwind-abort.rs:7:15`
Ensure that the const-eval engine handles `#[unwind(aborts)]` 2020-10-03 15:09:43 -07:00			`\|`
Change CTFE backtraces to use `note` instead of `label` to preserve their order labels are reordered within the file in which they are reported, which can mess up the stack trace 2022-11-29 13:10:42 +00:00			`LL \| const _: () = foo();`
			`\| ^^^^^`
Mention first and last macro in backtrace 2022-06-20 19:25:52 -07:00			= note: this error originates in the macro `$crate::panic::panic_2015` which comes from the expansion of the macro `panic` (in Nightly builds, run with -Z macro-backtrace for more info)
Ensure that the const-eval engine handles `#[unwind(aborts)]` 2020-10-03 15:09:43 -07:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Ensure that the const-eval engine handles `#[unwind(aborts)]` 2020-10-03 15:09:43 -07:00
Emit a hard error when a panic occurs during const-eval Previous, a panic during const evaluation would go through the `const_err` lint. This PR ensures that such a panic always causes compilation to fail. 2021-05-25 20:54:59 -05:00			For more information about this error, try `rustc --explain E0080`.