diff options
| author | Manish Goregaokar <manishsmail@gmail.com> | 2020-07-02 15:55:52 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-07-02 15:55:52 -0700 |
| commit | 65342fd341f63bb2b594a47436c7591f2ebc0208 (patch) | |
| tree | 4d2dc15d466ea51888fa4c43c6b1b096e7379486 /src/libstd/sys/unix/stack_overflow.rs | |
| parent | dc6a19c2f0a527826e6704e0ee7bfe7f2d7d7864 (diff) | |
| parent | 838c497a4578bb4c939e9834240198e22815ad1b (diff) | |
| download | rust-65342fd341f63bb2b594a47436c7591f2ebc0208.tar.gz rust-65342fd341f63bb2b594a47436c7591f2ebc0208.zip | |
Rollup merge of #73724 - CryZe:wasm-saturating-casts, r=alexcrichton
Use WASM's saturating casts if they are available WebAssembly supports saturating floating point to integer casts behind a target feature. The feature is already available on many browsers. Beginning with 1.45 Rust will start defining the behavior of floating point to integer casts to be saturating as well. For this Rust constructs additional checks on top of the `fptoui` / `fptosi` instructions it emits. Here we introduce the possibility for the codegen backend to construct saturating casts itself and only fall back to constructing the checks ourselves if that is not possible. Resolves part of #73591
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions