|
From: Cristian O. <one...@gm...> - 2010-09-23 07:19:35
|
On Thu, Sep 23, 2010 at 12:32 AM, John Reiser <jr...@bi...> wrote: > On 09/22/2010, Cristian Oneţ wrote: >> vex amd64->IR: unhandled instruction bytes: 0xF3 0xF 0xB8 0x4 0x11 0x48 > > The first five bytes are: popcnt (%rcx,%rdx,1),%eax > > On 09/20/2010, Julian Seward wrote: >> cat /proc/cpuinfo on the cpu emulated since r2011 says >> >> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca mov >> pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm >> constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf >> pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm >> sse4_1 sse4_2 popcnt aes lahf_lm ida arat tpr_shadow vnmi flexpriority ept >> vpid > > Note that 'popcnt' is in the list [so is 'aes'.] However, there is > no case for 0x0F 0xB8 in file VEX/priv/guest_x86_toIR.c. Oops. > [It doesn't help that there is an "extra" 0xF3 prefix.] > Could this be said in a more valgrind user understandable language? If I understand correctly it is a bug in valgrind? Should I file bugreport? Or is there anyother way I could help to get this fixed? Thanks! Regards, Cristian Oneţ |