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
From derek.br...@gmail.com on February 24, 2009 14:51:17
this was PR 278248
To avoid DR failing on the latest ISA changes we should consider adding runtime options that can be used as workarounds.
An event on an invalid opcode is not good enough: if we get the length wrong we can mess up later on. Need a way to specify ISA changes up front.
We'd need some kind of language. For example, for adding support for the 3-byte-opcode SSSE3 instructions we might support an option like this:
-opcode "0x0f 0x38 * modrm"
Both fast and slow decode paths would have to honor the option before the built-in decode tables.
Original issue: http://code.google.com/p/dynamorio/issues/detail?id=57
The text was updated successfully, but these errors were encountered:
No branches or pull requests
From derek.br...@gmail.com on February 24, 2009 14:51:17
this was PR 278248
To avoid DR failing on the latest ISA changes we should consider adding
runtime options that can be used as workarounds.
An event on an invalid opcode is not good enough: if we get the length
wrong we can mess up later on. Need a way to specify ISA changes up front.
We'd need some kind of language. For example, for adding support for the
3-byte-opcode SSSE3 instructions we might support an option like this:
-opcode "0x0f 0x38 * modrm"
Both fast and slow decode paths would have to honor the option before the
built-in decode tables.
Original issue: http://code.google.com/p/dynamorio/issues/detail?id=57
The text was updated successfully, but these errors were encountered: