-
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
Too wide memory load causes System.AccessViolationException on x64 and ARM64 platforms #78272
Comments
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsHi! I faced with
I tried it using .NET SDK 7.0.100 on different platforms, the results are as follows (w/ macos-x64:
macos-arm64:
linux-x64:
linux-arm64:
windows-arm64:
Nevertheless it works on windows-x64, here is its disasm:
Linked issues: #76194.
|
Same problem as #76194. |
Please note that unlike #76194 it also appears on different platforms (Windows, Linux, macOS) and architectures, and does not use |
It is expected we will see this bug on cited platforms, since their ABIs (unlike, say, Unix x86 or Windows x64) call for returning structs 3, 5, 6, 7 bytes in size in a single register. |
This and a similar bug existed in .NET since like .NET Framework 3.5 I think, it's just that |
|
Fixed with #76341 |
Hi!
I faced with
System.AccessViolationException
when reading 6-byte structure in .NET 7 app on Windows ARM64, Linux x64/ARM64, and macOS x64/ARM64, here is demo app:I tried it using .NET SDK 7.0.100 on different platforms, the results are as follows (w/
COMPlus_JitDisasm
enabled):macos-x64:
macos-arm64:
linux-x64:
linux-arm64:
windows-arm64:
Nevertheless it works on windows-x64, here is its disasm:
Linked issues: #76194.
The text was updated successfully, but these errors were encountered: