Integrate ARM plan9asm support in llgo#1717
Conversation
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly enhances Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request integrates ARM plan9asm support and adds build infrastructure for ARM baremetal targets. The changes are extensive, touching the build system, plan9asm translator, and runtime. The logic for conditional compilation of assembly files and handling of alternative packages for ARM seems correct. The addition of manual signatures for internal/bytealg on ARM is a key part of this. However, there is a critical issue in the new ARM atomic implementation (runtime/internal/lib/internal/runtime/atomic/atomic_llgo_arm.go), where the atomic operations are not actually atomic. This makes them unsafe for any multi-threaded environment. While this might be a placeholder for single-threaded baremetal targets, the build tag //go:build arm is too broad and suggests it applies to all ARM targets. This needs to be addressed. I've also included a minor suggestion for code consistency.
|
Good work wiring up ARM plan9asm support with solid test coverage for the new signatures and helper functions. The baremetal stubs are well-organized with correct build tag exclusions. A few areas need attention:
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1717 +/- ##
=======================================
Coverage 93.15% 93.16%
=======================================
Files 48 48
Lines 13350 13367 +17
=======================================
+ Hits 12436 12453 +17
Misses 727 727
Partials 187 187 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
8a54b80 to
830986c
Compare
Summary
Testing
Notes