Skip to content

Inline a few libcall impls into their raw wrappers regardless of CGU slicing - #14940

Merged
fitzgen merged 1 commit into
bytecodealliance:mainfrom
fitzgen:inline-libcall-impls-into-raw-libcall-wrappers
Oct 22, 2026
Merged

fitzgen merged 1 commit into
bytecodealliance:mainfrom
fitzgen:inline-libcall-impls-into-raw-libcall-wrappers

Conversation

@fitzgen

@fitzgen fitzgen commented Oct 22, 2026

Copy link
Copy Markdown
Member

Otherwise, changing CGU slicing can change whether these do or don't get inlined in practice, which makes for regressions on host-heavy benchmarks (e.g. benchmarks that spend a bunch of time in GC).

Fixes bytecodealliance/are-we-fast-yet#8

See also bytecodealliance/sightglass#348

…slicing

Otherwise, changing CGU slicing can change whether these do or don't get inlined
in practice, which makes for regressions on host-heavy
benchmarks (e.g. benchmarks that spend a bunch of time in GC).

Fixes bytecodealliance/are-we-fast-yet#8

See also bytecodealliance/sightglass#348
@fitzgen
fitzgen requested a review from a team as a code owner October 22, 2026 16:58
@fitzgen
fitzgen requested review from dicej and removed request for a team October 22, 2026 16:58
@fitzgen
fitzgen added this pull request to the merge queue Oct 22, 2026
Merged via the queue into bytecodealliance:main with commit e561d3d Oct 22, 2026
53 checks passed
@fitzgen
fitzgen deleted the inline-libcall-impls-into-raw-libcall-wrappers branch October 22, 2026 18:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Performance regression in f031a62ff4cd..f157b3e0302b (are-we-fast-yet run 00027)

2 participants