The compiler needs work

[xtremegamer1]

There are some issues right now with the compiler. For example, many VTIL instructions and more exotic native registers lack implementation. Also, making vexit compile into a "ret" is a bad idea. I think it would make more sense to compile into an unconditional jmp to the operand of the vexit. Whoever wrote the compiler seems to think that VTIL routines should be subroutines with their own stack frame, but at least with vmprotect it makes more sense to think of them as code that could be executed inline with the native code wrapping vmenters, because a single vmenter rarely (maybe never?) represents a routine with its own stack frame and instead represent snippets of code that modify the stack of the "caller" (vmenterer?) I am not sure the facilities provided by asmjit for virtual register allocation are best suited to this project because they seem to be bound to the notion of a function with its own stack, perhaps a custom one will need to be built or a different library used.

[xtremegamer1]

i will make a pr if i can manage to get my fork working. I would call the compiler half complete but that would be generous, it is more like 40% done.

[mrexodia]

Yeah it was just some POC code from the Discord that I didn’t want to get lost. Improvements are definitely welcome!

[xtremegamer1]

Sorry for making this rude issue. I appreciate the work you and others have put into this

[mrexodia]

Haha, no worries ^^

…

On Fri, 18 Nov 2022 at 12:07, sussy baka ***@***.***> wrote: Sorry for making this rude issue. I appreciate the work you and others have put into this — Reply to this email directly, view it on GitHub <#7 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AASYFGJW7TYRKKGW3BTD45DWI5IMLANCNFSM6AAAAAAR3G6KOM> . You are receiving this because you commented.Message ID: ***@***.***>