about summary refs log tree commit diff
path: root/src/rustllvm/RustWrapper.cpp
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2013-12-13 12:56:36 -0800
committerbors <bors@rust-lang.org>2013-12-13 12:56:36 -0800
commit378897a09c4c72595d450f74f2ffbb1ab44958a2 (patch)
tree029b82798846a0addae26001a7fa831e5f40aa54 /src/rustllvm/RustWrapper.cpp
parentae3078ca257fe39a7fdc84bdfb81778b2542c520 (diff)
parent667d114f47ae658894c496dbf07a8d29c737c877 (diff)
downloadrust-378897a09c4c72595d450f74f2ffbb1ab44958a2.tar.gz
rust-378897a09c4c72595d450f74f2ffbb1ab44958a2.zip
auto merge of #10916 : alexcrichton/rust/nounwind, r=pcwalton
When performing LTO, the rust compiler has an opportunity to completely strip
all landing pads in all dependent libraries. I've modified the LTO pass to
recognize the -Z no-landing-pads option when also running an LTO pass to flag
everything in LLVM as nothrow. I've verified that this prevents any and all
invoke instructions from being emitted.

I believe that this is one of our best options for moving forward with
accomodating use-cases where unwinding doesn't really make sense. This will
allow libraries to be built with landing pads by default but allow usage of them
in contexts where landing pads aren't necessary.
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions