We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Should the Mem constructor that takes base and index registers have scale set to 1 instead of 0?
zasm/include/zasm/x86/memory.hpp
Line 27 in 012062f
Succeeds:
a.mov(zasm::x86::al, zasm::x86::byte_ptr(zasm::x86::rsi, zasm::x86::rcx, 1, 0));
Fails impossible instruction:
a.mov(zasm::x86::al, zasm::x86::byte_ptr(zasm::x86::rsi, zasm::x86::rcx));
Likely cause:
// ptr [base + index] // ex.: mov eax, ptr [ecx+edx] static constexpr Mem ptr(BitSize bitSize, const Gp& base, const Gp& index) noexcept { return Mem(bitSize, Seg{}, base, index, 0, 0); }
The text was updated successfully, but these errors were encountered:
I will have to look into that, I remember there was a special case about this.
Sorry, something went wrong.
Merge pull request #125 from zyantific/fix-124
43d42bb
Fix #124: memory scale defaulting to 0 rather than 1 when index is supplied
I've merged the change so its now 1 by default when index is supplied, thanks for the reporting the issue.
Successfully merging a pull request may close this issue.
Should the Mem constructor that takes base and index registers have scale set to 1 instead of 0?
zasm/include/zasm/x86/memory.hpp
Line 27 in 012062f
Succeeds:
Fails impossible instruction:
Likely cause:
The text was updated successfully, but these errors were encountered: