Skip to content

Conversation

@wenyongh
Copy link
Collaborator

No description provided.

@lum1n0us
Copy link
Contributor

Still have a question, do we prevent those JitReg, like using eax, edx, from register allocation by satisfying the requirement of jit_cc_is_hreg? It will help us to keep a JitReg's hardware register till the codegen phase.

But how to make sure those hardware registers, edx, eax, won't be used by other JitReg when special cases, like div, is happening?

@wenyongh wenyongh changed the title [WIP] Implement i32/i64 div and rem opcodes translation Implement i32/i64 div and rem opcodes translation Apr 18, 2022
@wenyongh wenyongh merged commit 5f0fab0 into bytecodealliance:dev/fast_jit Apr 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants