rust/src/libunwind
bors 5c41fcec4c Auto merge of #47571 - FenrirWolf:libunwind, r=alexcrichton
Match libunwind's EABI selection with libpanic_unwind

Currently, the `libunwind` crate will only select the ARM EABI if it is compiling for ARM/Linux or Android targets. `libpanic_unwind`, however, will choose the ARM EABI if the target arch is ARM and the OS is not iOS. This means that if one tries to enable unwinding for a non-standard ARM target (such as implementing a custom stdlib via Xargo, for example), then the two crates can potentially disagree about which EABI is being targeted.

This PR makes `libunwind` use the [same logic](https://github.com/rust-lang/rust/blob/master/src/libpanic_unwind/gcc.rs#L139-L146) as `libpanic_unwind` when choosing the EABI.

I noticed there are a few comments about certain functions only differing on Android or ARM/Linux, but I *think* that those differences apply to the ARM EABI in general. Let me know if I'm wrong about that.
2018-01-27 00:28:34 +00:00
..
build.rs Link against -lunwind on CloudABI. 2017-12-26 23:32:42 +01:00
Cargo.toml
lib.rs std: Add a new wasm32-unknown-unknown target 2017-11-19 21:07:41 -08:00
libunwind.rs Match libunwind's EABI selection with libpanic_unwind 2018-01-19 02:26:03 -07:00
macros.rs std: Add a new wasm32-unknown-unknown target 2017-11-19 21:07:41 -08:00