diff options
| author | bors <bors@rust-lang.org> | 2019-10-12 02:31:03 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2019-10-12 02:31:03 +0000 |
| commit | 4b42e919d640f7c714a7e87c91b4f3a9089552d0 (patch) | |
| tree | a4e7dc818358e548ca505d9c67fff6e85bd6c5b5 /src/test/ui/iterators/iter-sum-overflow-debug.rs | |
| parent | 6767d9b90b6b630ad8e2a9e5e02fd74c00c98759 (diff) | |
| parent | 028f53e38e5830897693ea3644c672a096cfa0ec (diff) | |
| download | rust-4b42e919d640f7c714a7e87c91b4f3a9089552d0.tar.gz rust-4b42e919d640f7c714a7e87c91b4f3a9089552d0.zip | |
Auto merge of #65020 - pnkfelix:targetted-fix-for-always-marking-rust-abi-unwind-issue-64655, r=alexcrichton
Always mark rust and rust-call abi's as unwind PR #63909 identified a bug that had been injected by PR #55982. As discussed on https://github.com/rust-lang/rust/issues/64655#issuecomment-537517428 , we started marking extern items as nounwind, *even* extern items that said they were using "Rust" or "rust-call" ABI. This is a more targeted variant of PR #63909 that fixes the above bug. Fix #64655 ---- I personally suspect we will want PR #63909 to land in the long-term But: * it is not certain that PR #63909 *will* land, * more importantly, PR #63909 almost certainly will not be backported to beta/stable. The identified bug was more severe than I think anyone realized (apart from perhaps @gnzlbg, as noted [here](https://github.com/rust-lang/rust/pull/63909#issuecomment-524818838)). Thus, I was motivated to write this PR, which fixes *just* the issue with extern rust/rust-call functions, and deliberately avoids injecting further deviation from current behavior (you can see further notes on this in the comments of the code added here).
Diffstat (limited to 'src/test/ui/iterators/iter-sum-overflow-debug.rs')
0 files changed, 0 insertions, 0 deletions