Mark uint::wrapping_next_power_of_two as #[inline]

[aDotInTheVoid]

This brings it in line with next_power_of_two and checked_next_power_of_two

https://godbolt.org/z/Tr18GnqKj

Output as of `rustc 1.61.0-nightly (4ce3749 2022-02-28)`

example::npot:
        lea     eax, [rdi - 1]
        movzx   eax, al
        lzcnt   ecx, eax
        add     ecx, -24
        mov     al, -1
        shr     al, cl
        inc     al
        cmp     dil, 2
        movzx   ecx, al
        mov     eax, 1
        cmovae  eax, ecx
        ret

example::cnpot:
        lea     eax, [rdi - 1]
        movzx   eax, al
        lzcnt   ecx, eax
        add     ecx, -24
        mov     al, -1
        shr     al, cl
        xor     ecx, ecx
        cmp     dil, 2
        movzx   edx, al
        cmovb   edx, ecx
        inc     dl
        setne   al
        ret

example::wrapping_next_power_of_two:
        jmp     qword ptr [rip + _ZN4core3num20_$LT$impl$u20$u8$GT$26wrapping_next_power_of_two17hd879a85055735264E@GOTPCREL]

[rust-highfive]

r? @yaahc

(rust-highfive has picked a reviewer for you, use r? to override)

[yaahc]

Pretty sure this will be fine but I do wanna do a quick check to see if this impacts perf anywhere

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

@rustbot label: +S-waiting-on-perf

[bors]

⌛ Trying commit 3f04c85 with merge 85382c1fc220067f45716e68535acb80754162c9...

[bors]

☀️ Try build successful - checks-actions
Build commit: 85382c1fc220067f45716e68535acb80754162c9 (85382c1fc220067f45716e68535acb80754162c9)

[rust-timer]

Queued 85382c1fc220067f45716e68535acb80754162c9 with parent 1bfe40d, future comparison URL.

[rust-timer]

Finished benchmarking commit (85382c1fc220067f45716e68535acb80754162c9): comparison url.

Summary: This benchmark run did not return any relevant results. 2 results were found to be statistically significant but too small to be relevant.

If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf.

Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR led to changes in compiler perf.

@bors rollup=never
@rustbot label: +S-waiting-on-review -S-waiting-on-perf -perf-regression

[yaahc]

alright, that's pretty much what I expected to see.

Thank you for the PR!

@bors r+

[bors]

📌 Commit 3f04c85 has been approved by yaahc

[bors]

⌛ Testing commit 3f04c85 with merge a3293c1e2ab78d18cb6fe64ae12901938c18ce8b...

[bors]

💥 Test timed out

[rust-log-analyzer]

A job failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)

[yaahc]

@bors retry

[bors]

⌛ Testing commit 3f04c85 with merge 1a2ba5044a62efff3fc319edb16197110b6b6bb8...

[rust-log-analyzer]

The job x86_64-gnu-llvm-12 failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)

[bors]

💔 Test failed - checks-actions

[yaahc]

uuuuh, not sure what's going on with that test failure...

[bors]

⌛ Testing commit 3f04c85 with merge 4b133a7...

[bors]

☀️ Test successful - checks-actions
Approved by: yaahc
Pushing 4b133a7 to master...

[rust-timer]

Finished benchmarking commit (4b133a7): comparison url.

Summary: This benchmark run did not return any relevant results.

If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf.

@rustbot label: -perf-regression