diff options
| author | Guillaume Gomez <guillaume1.gomez@gmail.com> | 2023-06-15 22:04:55 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-06-15 22:04:55 +0200 |
| commit | ab314a57fa6141d1c5436fb6dbb500adbde3e64b (patch) | |
| tree | 8ceab61426ddd133cbf1799430908c33eada6cba /tests/codegen/src-hash-algorithm/src-hash-algorithm-sha1.rs | |
| parent | 331249a94930adb3d2a7243d946733b63324b2d6 (diff) | |
| parent | d9531a0d93f63a8e67e56419e0aadf25a0edd43a (diff) | |
| download | rust-ab314a57fa6141d1c5436fb6dbb500adbde3e64b.tar.gz rust-ab314a57fa6141d1c5436fb6dbb500adbde3e64b.zip | |
Rollup merge of #112403 - nbdd0121:eh_frame, r=Nilstrieb
Prevent `.eh_frame` from being emitted for `-C panic=abort` Since `CheckAlignment` pass is after the `AbortUnwindingCalls` pass, the `UnwindAction::Terminate` inserted in it has no chance to be converted to `UnwindAction::Unreachable` anymore, causing us to emit landing pads that are not necessary. Although these landing pads can themselves be eliminated by LLVM, `.eh_frame` sections are still generated. This causes trouble for Rust-for-Linux project recently. This PR changes it to generate `UnwindAction::Terminate` when we opt for `-Cpanic=unwind`, and `UnwindAction::Unreachable` for `-Cpanic=abort`. `@ojeda`
Diffstat (limited to 'tests/codegen/src-hash-algorithm/src-hash-algorithm-sha1.rs')
0 files changed, 0 insertions, 0 deletions