Skip to content

JIT: Disable old promotion for structs with significant padding#104438

Merged
jakobbotsch merged 3 commits intodotnet:mainfrom
jakobbotsch:avoid-old-promotion-with-significant-padding
Jul 5, 2024
Merged

JIT: Disable old promotion for structs with significant padding#104438
jakobbotsch merged 3 commits intodotnet:mainfrom
jakobbotsch:avoid-old-promotion-with-significant-padding

Conversation

@jakobbotsch
Copy link
Member

When old promotion kicks in for structs with significant padding it generally results in dependent promotion as block morphing handles these conservatively. Disable this case and allow physical promotion to handle it instead.

When old promotion kicks in for structs with significant padding it
generally results in dependent promotion as block morphing handles these
conservatively. Disable this case and allow physical promotion to handle
it instead.
@ghost ghost added the area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI label Jul 4, 2024
@dotnet-policy-service
Copy link
Contributor

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

@jakobbotsch jakobbotsch marked this pull request as ready for review July 4, 2024 19:18
@jakobbotsch
Copy link
Member Author

cc @dotnet/jit-contrib PTAL @EgorBo

Diffs. More impactful in crossgen2 since there we consider more structs to have significant padding (due to versionability) and thus there more structs will get better handling.

@jakobbotsch jakobbotsch merged commit 8a99ada into dotnet:main Jul 5, 2024
@jakobbotsch jakobbotsch deleted the avoid-old-promotion-with-significant-padding branch July 5, 2024 11:41
@github-actions github-actions bot locked and limited conversation to collaborators Aug 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants