diff options
| author | bors <bors@rust-lang.org> | 2021-09-13 22:14:57 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2021-09-13 22:14:57 +0000 |
| commit | 9f85cd6f2ab2769c16e89dcdddb3e11d9736b351 (patch) | |
| tree | 75331189ed48a97105bb5782534240c5844f7afb /compiler/rustc_query_impl/src | |
| parent | 9bb77da74dac4768489127d21e32db19b59ada5b (diff) | |
| parent | 4d66fbc4b9b95a652636e3723937c3accec85d65 (diff) | |
| download | rust-9f85cd6f2ab2769c16e89dcdddb3e11d9736b351.tar.gz rust-9f85cd6f2ab2769c16e89dcdddb3e11d9736b351.zip | |
Auto merge of #87794 - bonega:enum_niche_prefer_zero, r=nagisa
Enum should prefer discriminant zero for niche
Given an enum with unassigned zero-discriminant, rust should prefer it for niche selection.
Zero as discriminant for `Option<Enum>` makes it possible for LLVM to optimize resulting asm.
- Eliminate branch when expected value coincides.
- Use smaller instruction `test eax, eax` instead of `cmp eax, ?`
- Possible interaction with zeroed memory?
Example:
```rust
pub enum Size {
One = 1,
Two = 2,
Three = 3,
}
pub fn handle(x: Option<Size>) -> u8 {
match x {
None => {0}
Some(size) => {size as u8}
}
}
```
In this case discriminant zero is available as a niche.
Above example on nightly:
```asm
mov eax, edi
cmp al, 4
jne .LBB0_2
xor eax, eax
.LBB0_2:
ret
```
PR:
```asm
mov eax, edi
ret
```
I created this PR because I had a performance regression when I tried to use an enum to represent legal grapheme byte-length for utf8.
Using an enum instead of `NonZeroU8` [here](https://github.com/bonega/yore/blob/d683304f5dfe2e99f769e6ab8adf8d60a0d1d9b3/src/internal/decoder_incomplete.rs#L90)
resulted in a performance regression of about 5%.
I consider this to be a somewhat realistic benchmark.
Thanks to `@ogoffart` for pointing me in the right direction!
Edit: Updated description
Diffstat (limited to 'compiler/rustc_query_impl/src')
0 files changed, 0 insertions, 0 deletions
