|
From: Christoph B. <bar...@or...> - 2006-09-30 10:46:14
|
Hi, I get the message: vex amd64->IR: unhandled instruction bytes: 0xF2 0x4C 0xF 0x10 Is this a valgrind error? Christoph |
|
From: Julian S. <js...@ac...> - 2006-09-30 10:50:01
|
On Saturday 30 September 2006 11:46, Christoph Bartoschek wrote: > Hi, > > I get the message: > > vex amd64->IR: unhandled instruction bytes: 0xF2 0x4C 0xF 0x10 > > Is this a valgrind error? In which version? J |
|
From: Christoph B. <bar...@or...> - 2006-09-30 10:53:01
|
Am Samstag, 30. September 2006 12:49 schrieb Julian Seward: > On Saturday 30 September 2006 11:46, Christoph Bartoschek wrote: > > Hi, > > > > I get the message: > > > > vex amd64->IR: unhandled instruction bytes: 0xF2 0x4C 0xF 0x10 > > > > Is this a valgrind error? > > In which version? > > J Valgrind 3.2.1, compiled from sources. The code comes from the Intel Math Kernel Library. Christoph |
|
From: Nicholas M. <nm...@gm...> - 2006-10-01 00:09:53
|
On Sat, 30 Sep 2006 12:53:02 +0200, Christoph Bartoschek wrote: > Am Samstag, 30. September 2006 12:49 schrieb Julian Seward: >> On Saturday 30 September 2006 11:46, Christoph Bartoschek wrote: >> > Hi, >> > >> > I get the message: >> > >> > vex amd64->IR: unhandled instruction bytes: 0xF2 0x4C 0xF 0x10 >> > >> > Is this a valgrind error? >> >> In which version? >> >> J > > Valgrind 3.2.1, compiled from sources. The code comes from the Intel Math > Kernel Library. > > Christoph > The instruction is incomplete, but it looks like it's a SSE2 MOVSD with ModRM and SIB bytes (MOVSD always takes a ModRM byte, and the REX.X prefix implies the existence of a SIB byte). |