consider cpuid features when deciding invalid instrs

From [email protected] on April 11, 2011 10:37:32

currently the DR encoder will not consider a new opcode as invalid when running on an older processor that does not have that feature. this isn't a serious problem for DR itself since the right thing will happen when treating an invalid instr as valid: it's the other way around that causes often-fatal problems. but for DR as a disassembly library and for precision it would be nice to consider the cpuid features of the current processor. the feature set to assume may have to become a global setting when decoding statically.

Original issue: http://code.google.com/p/dynamorio/issues/detail?id=431