-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Q: highly likely incorrect aarch64 ldaxrh instruction disassembly #788
Comments
Disassembling in gem5 has some known issues... I am sure the reason why we are printing in that format is because MemoryEx64 is shared between load and store exclusive. The clean solution would be to provide a different generateDisassembly implementation for load exclusive. This should definitely be fixed so I am keeping the issue open, but I regard this as low priority: I will deal with it when I'll have some free time. FYI To mitigate the annoyance of dealing with an incorrect disassembly we integrated gem5 with the capstone disassembler: #494 Hope this helps. |
Thank you @giactra ! |
Hello, the code in the latest stable trunk
src/arch/arm/insts/mem64.cc
generates a disassembly for the aarch64 instruction
ldaxrh
e.g.with 3 operands instead of 2 follow the ARM reference.
Android toolchain fails to assembly the generated disassembly as expects two operands for the instruction instead of given 3.
I would rather expect to see here:
The text was updated successfully, but these errors were encountered: