Aurelien Jarno wrote: > It is not a full fix, as the OS can actually use any instruction that > always generate a trap (even a memory access) as an instruction barrier > to make sure the following instructions are never executed. This > actually affects all targets, but is unlikely to happen.
I'm sure I've seen code wich intentionally accesses invalid memory, followed by non-instruction data such as a message to print. But I can't think where. > One solution for that would be to only generate an exception for an > unsupported instruction when it is the first instruction of a TB, and > otherwise just end the translation before this instruction. Because that's a simple general solution for all targets, it sounds like a good idea to me. -- Jamie
