about summary refs log tree commit diff
path: root/library/std/src/sys/unix/alloc.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2021-04-11 19:50:19 +0000
committerbors <bors@rust-lang.org>2021-04-11 19:50:19 +0000
commita8661245649f3d1c0dc5b23270bdac0bbd2d8f64 (patch)
tree2745fde13d5cd97d43de9a28e521956fb8cb050e /library/std/src/sys/unix/alloc.rs
parent7953910464e073eb3876d1544a3fd5b5ba0ca49b (diff)
parent2fd4dd20d717b3e8af4bdff2873b348920426425 (diff)
downloadrust-a8661245649f3d1c0dc5b23270bdac0bbd2d8f64.tar.gz
rust-a8661245649f3d1c0dc5b23270bdac0bbd2d8f64.zip
Auto merge of #83482 - hyd-dev:uwtable, r=nagisa
Allow using `-C force-unwind-tables=no` when `panic=unwind`

It seems LLVM still generates proper unwind tables even there is no `uwtable` attribute, unless I looked at the wrong place :thinking::
https://github.com/llvm/llvm-project/blob/c21016715f0ee4a36affdf7150ac135ca98b0eae/llvm/include/llvm/IR/Function.h#L666

Therefore, I *assume* it's safe to omit `uwtable` even when `panic=unwind`, and this PR removes the restriction that disallows using `-C force-unwind-tables=no` when `panic=unwind`.
Diffstat (limited to 'library/std/src/sys/unix/alloc.rs')
0 files changed, 0 insertions, 0 deletions