-
Notifications
You must be signed in to change notification settings - Fork 18.1k
Add missing ARM64 instructions to Go ASM #71701
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
this doesn't look like a concrete bug. |
@seankhliao the goal wasn't about reporting a bug but checking if the team is OK getting help to implement the instructions. I made this issue out of courtesy. Does this mean this is not needed and I should stop working on this? |
This is probably a duplicate of #44734. |
This is not a duplicate per se because I was just thinking about adding the instructions and tests like it has been done up until now. However, I can see the appeal to redesign the framework for arm64 assembler to also support SVE and easier maintenance. Let me read about it more, and I'll get back to you. |
@randall77 while this seems very interesting, the redesign seems to be something for people who have more expertise in the ISA design (maybe people at Arm) and that have more time to spend on this than me. If you still want, I can try to add the instructions that are mentioned in the related issues but otherwise, I'll stop working on this. |
I think it would be ok to add particular instructions to the existing assembler if there is a need for them. |
Uh oh!
There was an error while loading. Please reload this page.
After finally learning how to add instructions to Go ASM, I want to contribute to adding missing instructions for ARM64.
I'm aware of some of them missing in the SIMD land (e.g. #41092) but I'm also open to suggestions from people.
If there is any objection, let me know and I will stop working on this.
To follow the work you can check: https://github.com/Clement-Jean/go/tree/missing_arm64_instructions
The text was updated successfully, but these errors were encountered: