Skip to content
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.

Sign up for GitHub

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

Jump to bottom

cmd/objdump: MOVZX disassembly is ambiguous #52171

Open
randall77 opened this issue Apr 5, 2022 · 0 comments
Open

cmd/objdump: MOVZX disassembly is ambiguous #52171

randall77 opened this issue Apr 5, 2022 · 0 comments
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsFix The path to resolution is known, but the work has not been done.
Milestone
Backlog

Comments

@randall77
Copy link
Contributor

Is it zeroing the top 56, 48, or 32 bits? Not clear from the disassembler.
Similarly for MOVSX - where is it sign-extending from?
In gcc syntax you can tell from the size of the register argument. Not so for plan9 syntax.

I fixed something similar for POPCNT in https://go-review.googlesource.com/c/arch/+/351889/ , but that strategy won't work here because the size used there is the output size, not the input size.
@randall77 randall77 added the NeedsFix The path to resolution is known, but the work has not been done. label Apr 5, 2022
@randall77 randall77 added this to the Backlog milestone Apr 5, 2022
@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Jul 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsFix The path to resolution is known, but the work has not been done.
Projects
Go Compiler / Runtime
Status: Triage Backlog
Milestone
Backlog
Development

No branches or pull requests
2 participants
@randall77 @gopherbot