Correct Windows Arm64 minimum hardware requirements - #55453
Open
tannergooding wants to merge 2 commits into
Open
Correct Windows Arm64 minimum hardware requirements#55453tannergooding wants to merge 2 commits into
tannergooding wants to merge 2 commits into
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the .NET 11 breaking-change documentation to reflect that Windows Arm64 JIT/NativeAOT minimum hardware remains armv8.0-a, while the Windows Arm64 ReadyToRun target remains higher and can fall back to JIT on older supported devices.
Changes:
- Clarifies that the x86/x64 minimum baseline update (to
x86-64-v2) is the primary “minimum hardware” breaking change. - Updates the Windows Arm64 section to state there’s no minimum-hardware baseline change and explains ReadyToRun fallback-to-JIT behavior.
- Adjusts the “New behavior,” “Reason for change,” and “Recommended action” sections to distinguish x86/x64 baseline failures from Arm64 ReadyToRun fallback behavior.
Show a summary per file
| File | Description |
|---|---|
| docs/core/compatibility/jit/11/minimum-hardware-requirements.md | Corrects Windows Arm64 minimum-hardware messaging and clarifies ReadyToRun targeting and fallback behavior. |
Review details
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
- Files reviewed: 1/1 changed files
- Comments generated: 2
- Review effort level: Lite
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Sawsqr68
approved these changes
Aug 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Correct the .NET 11 minimum-hardware documentation after dotnet/runtime#132345 restored the Windows Arm64 JIT and NativeAOT baseline to
armv8.0-a.The Windows Arm64 ReadyToRun target remains
armv8.2-a + RCPC. The document now explains that supported devices below that target continue to run by falling back to JIT compilation.Note
This pull request was created with GitHub Copilot.
Internal previews