about summary refs log tree commit diff
path: root/src/libstd/sys/unix/stack_overflow.rs
diff options
context:
space:
mode:
authorManish Goregaokar <manishsmail@gmail.com>2020-06-28 08:30:29 -0700
committerGitHub <noreply@github.com>2020-06-28 08:30:29 -0700
commit95da53f7fd7434f2cb13b069d4e26b961879cf65 (patch)
tree4449e0819fbcf482324adfa50a968ff7a39e0d0c /src/libstd/sys/unix/stack_overflow.rs
parent2c1b7329611f0310ed18dd9bb6dea99cd42302c1 (diff)
parent4c14f9d110478edcb2d0c3e1cda73937fc3b3d6e (diff)
downloadrust-95da53f7fd7434f2cb13b069d4e26b961879cf65.tar.gz
rust-95da53f7fd7434f2cb13b069d4e26b961879cf65.zip
Rollup merge of #73800 - nikic:hash_i, r=kennytm
Forward Hash::write_iN to Hash::write_uN

The `Hasher::write_iN()` methods should forward to `Hasher::write_uN()`, because some Hasher implementations implement only the `write_uN()` variants, with the expectation that `write_iN()` will use the same implementation. Most notably, this is the case for the [FxHasher](https://github.com/rust-lang/rustc-hash/blob/5e09ea0a1c7ab7e4f9e27771f5a0e5a36c58d1bb/src/lib.rs#L111) used by rustc itself.

This used to be the case previously, but was broken in #59982. As the PR description makes no mention of this particular change, I assume it was unintentional.

In a local test, this mitigates the regression from #73526 on at least one test-case (cc @cuviper), because we're no longer at the mercy of `FxHasher::write()` getting inlined to get reasonable performance.
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions