docs: correct supported CPU targets - #1
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Code Review
This pull request updates the README.md to document the addition of experimental ARM64 Linux ELF cross-compilation support in the v1 compiler. It includes updated build target examples, details on verifying ARM64 output via qemu-user, and updates the feature matrix table to reflect experimental ARM64 support and the planned status of RISC-V. There are no review comments to address, and I have no further feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
…nt/docs-cpu-targets # Conflicts: # README.md Co-authored-by: Codesmith <codesmith-bot@users.noreply.github.com>
Corrects the README target claim to reflect the supported experimental ARM64 target and the absence of RISC-V support.
The prior table said all multi-architecture CPU support was unavailable even though the ARM64 backend is compiled, tested, and self-hosted through the v1 release gates.
Validation: ARM64 probe emitted static AArch64 ELF and exited 42 under qemu-aarch64-static; tests/run_native_arm64.sh passed 99/99.
Need help on this PR? Tag
/codesmithwith what you need. Autofix is enabled.