Florian Bernd

@athre0z How do we proceed with this PR?

Just go with undefined behavior is a bad idea, because it will often lead to invalid memory access or other critical side effects. We don't see these effects on master...

@tremalrik: The `XLAT` case currently can't be modelled in the data-tables. Our implicit memory operands only support a segment and a base register for now. This is why we used...

@tremalrik The `RMPUPDATE` expects a physical address in the register. For the reasons mentionied in https://github.com/zyantific/zydis/issues/181#issuecomment-907837389, I will keep the register here. In case of `MONITOR` and `UMONITOR` I think...

@athre0z Sure, meanwhile we could improve the documentation for these values. Although I think it already is quite understandable 😛 ```c /** * The operand is explicitly encoded in the...

Thanks for reporting. I'm aware of this problem and implementing a more advanced system for the flags is already on my todo-list (for the v3.0 release). Nevertheless some of these...

Allright. I can easily implement some logic for `RCL/RCR/ROL/ROR`, `SAL/SAR/SHL/SHR`, and `SHLD/SHRD` by adding an opcode-filter that matches the IMMEDIATE value of the instruction. `CLI/STI` is beyond the scope of...

Reminder for myself: Let's for now always include the conditional flags. For the register form of the rotate instructions we can't do much anyways ...

Thanks for reporting again! I will have a look on wednesday.

> Some instructions should use the address size not the operand size to select the register `clzero`/`vmload` Fixed with https://github.com/zyantific/zydis-db/commit/8d3d5272af45756ced9b927f1bc1be5924ecf68f > there are more similar instructions Could you please report...