-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[ppc64le] Performance improvements while branching during function calls #90367
Conversation
…l method for ppc64le architecture
/azp run runtime-community |
Azure Pipelines successfully started running 1 pipeline(s). |
green on ppc |
/backport to release/8.0-rc1 |
Started backporting to release/8.0-rc1: https://github.com/dotnet/runtime/actions/runs/5873025608 |
@directhex backporting to release/8.0-rc1 failed, the patch most likely resulted in conflicts: $ git am --3way --ignore-whitespace --keep-non-patch changes.patch
Applying: [ppc64le] Fixed thunk address 8 byte alignment issue
.git/rebase-apply/patch:41: trailing whitespace.
/* We need to align thunks_offset to 8 byte boundary, hence allocating first 8 bytes
warning: 1 line adds whitespace errors.
Using index info to reconstruct a base tree...
M src/mono/mono/mini/mini-ppc.c
M src/mono/mono/mini/mini-ppc.h
Falling back to patching base and 3-way merge...
Auto-merging src/mono/mono/mini/mini-ppc.h
Auto-merging src/mono/mono/mini/mini-ppc.c
CONFLICT (content): Merge conflict in src/mono/mono/mini/mini-ppc.c
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 [ppc64le] Fixed thunk address 8 byte alignment issue
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Error: The process '/usr/bin/git' failed with exit code 128 Please backport manually! |
@directhex an error occurred while backporting to release/8.0-rc1, please check the run log for details! Error: git am failed, most likely due to a merge conflict. |
@vargaz @directhex |
Why did the auto backport fail ? |
Weird, dunno, I didn't expect it to fail. |
Performance improvements has been made while branching during function calls by using bcctrl instruction instead of blrl instruction.