You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You're right that using an X dynamic register instead of an XSP dynamic register shouldn't allow this instruction to match at all, so something is going wrong here. I'll investigate.
Found the bug, that part of the code also allows non-XSP family registers through so normal registers that aren't the zero reg can be used. This exemption is needed for static registers (what family is X1, X or XSP), but it doesn't actually check that they're static so dynamic regs get a pass as well.
Easy fix, but will break working user code so probably have to cut a new release for this.
Hi,
I'm trying to generate some code like:
Dynasm successfully assembles this without reporting an error. However, the assembled code is:
Which is incorrect according to the documentation that specifies only the dynamic encoding prefix
XSP
should encode asp
operand.Is something like
add xzr, x1, #0x1
unencodable? If that's the case, maybe dynasm should return an error instead of generatingsp
silently.The text was updated successfully, but these errors were encountered: