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

AArch64: op.vas unset for mov v0.16b, v18.16b #1843

Closed
adamjseitz opened this issue Feb 25, 2022 · 1 comment
Closed

AArch64: op.vas unset for mov v0.16b, v18.16b #1843

adamjseitz opened this issue Feb 25, 2022 · 1 comment

Comments

@adamjseitz
Copy link
Contributor

The following mov instruction does not have the vas attribute set correctly in its operand details:

mov v0.16b, v18.16b

cstool -d arm64 '40 1e b2 4e'
 0  40 1e b2 4e  mov    v0.16b, v18.16b
        ID: 488 (mov)
        op_count: 2
                operands[0].type: REG = v0
                operands[0].access: WRITE
                operands[1].type: REG = v18
                operands[1].access: READ
        Registers read: v18
        Registers modified: v0
        Groups: neon

This is similar to the missing vas specifier in #1842.
@adamjseitz adamjseitz mentioned this issue Mar 21, 2022
Merged
@kabeor kabeor mentioned this issue Mar 22, 2022
Merged
adamjseitz added a commit to adamjseitz/capstone that referenced this issue Mar 22, 2022
@adamjseitz
Add AArch64 mov VAS specifier tests to cstest
05477a7 
Add four tests to the cstest suite to validate issue capstone-engine#1843 does not
regress. Additionally, update the way VAS specifiers are printed so
that the correct operand is verified.
@kabeor
Copy link
Member

kabeor commented Mar 23, 2022

solved，close now

@capstone-engine capstone-engine locked and limited conversation to collaborators Mar 23, 2022
@capstone-engine capstone-engine unlocked this conversation Mar 23, 2022
@kabeor kabeor closed this as completed Mar 23, 2022
@adamjseitz adamjseitz mentioned this issue Apr 25, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@adamjseitz @kabeor