-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JIT: Optimize Memmove unrolling for constant src #108576
Conversation
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
/azp run runtime-coreclr outerloop, runtime-coreclr jitstress, runtime-coreclr pgo |
Azure Pipelines successfully started running 3 pipeline(s). |
Co-authored-by: Jakob Botsch Nielsen <[email protected]>
PTAL @jakobbotsch @dotnet/jit-contrib |
@MihuBot -arm64 |
@EgorBo Regressions on arm64?
EgorBot/runtime-utils#110 (comment)
|
load might be faster than up to 4 instructions to compose a 64bit constant for "FALS" or "TRUE" utf16 strings on arm64, but it's tricky in the real world, the load might be under contention. Anyway, we'll see once dotnet/performance run finishes |
LowerCallMemmove
already does a good job unrolling Memmove. Unfortunately, it leaves some opportunities on the table when the source can be a constant (esp, GPR constant), so we can skip a memory load. The reason is thatLowerCallMemmove
cannot rely on VN for that as it's too late.Codegen diff:
Diffs