-
Notifications
You must be signed in to change notification settings - Fork 5k
Native AOT ARM32 lanes failing after docker update #113609
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
Comments
Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas |
It is not unusual to get breaks like this on major compiler version updates that come with new optimizations and uncover latent bugs. cc @richlander FYI: More clang 20 breaks. |
The fix replaces the native implementation of the native format decoder with the clone of the managed implementation. Fixes dotnet#113609
clang20 fuses two sequential int32 reads into a single |
I'm guessing that we (me) can already start the new PR (revert again) since the PR was merged today. Right? |
I have a pending PR with the fix for the known Arm32 NAOT issue: #113637 It makes sense to try again once that fix is merged. |
ARM32 outerloop is pretty broken after #113248: https://dev.azure.com/dnceng-public/public/_build?definitionId=265&_a=summar
I've submitted a revert at #113598 to confirm this is caused by the docker toolset update.
I pulled down a dump with runfo and this is a
Signal SIGBUS (Bus error) code BUS_ADRALN (Invalid address alignment) at 0x441a933
with stacks likeIt's not clear to me why the stack is broken. But unaligned access sounds reasonable, this data is definitely not 4-byte aligned (we do not align the EH info blob and most of the blob are variable length integers, making the initial blob alignment meaningless anyway)
It is not clear to my why this is a problem now and whether this is the only spot where we have a problem and how it could be caused by a toolset update.
Cc @dotnet/ilc-contrib
The text was updated successfully, but these errors were encountered: