[valgrind] [Bug 395246] vex amd64->IR: unhandled instruction bytes:

[Jouni Laakso]

https://bugs.kde.org/show_bug.cgi?id=395246

Jouni Laakso  changed:

   What|Removed |Added

 Resolution|--- |UNMAINTAINED
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Jouni Laakso  ---
32-bit error added to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228973
.  Unfortunately the version in 12-CURRENT is old. Even older version can be
found from an URL: https://bitbucket.org/stass/valgrind-freebsd/overview .
Where the ports version is I don't know. Compiling valgrind from source:

# ./autogen.sh 
running: aclocal
running: autoheader
running: automake -a
running: autoconf
# sh ./configure --prefix=/usr/local/valgrind
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ./install-sh -c -d
...
checking for gcc... no
checking for cc... cc
checking whether the C compiler works... yes
...
checking for a supported version of gcc... ok (clang-6.0.0)
checking build system type... x86_64-unknown-freebsd12.0
checking host system type... x86_64-unknown-freebsd12.0
checking for a supported CPU... ok (x86_64)
checking for a 64-bit only build... no
checking for a 32-bit only build... no
checking for a supported OS... no (freebsd12.0)
configure: error: Valgrind is operating system specific. Sorry.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 395246] vex amd64->IR: unhandled instruction bytes:

[Tom Hughes]

https://bugs.kde.org/show_bug.cgi?id=395246

Tom Hughes  changed:

   What|Removed |Added

 CC||t...@compton.nu

--- Comment #1 from Tom Hughes  ---
I don't how it is in any way similar to
https://bugs.kde.org/show_bug.cgi?id=373166 other than that both involved
unhandled instruction sequences.

Even that isn't the whole story because you've really reported two entirely
separate bugs here - fortunately only one of them is in scope here.

The 64 bit issue appears to be a vpmaskmovd instruction (0x8E with an 0x0F 0x38
prefix from the VEX prefix) which I suspect may be implemented now - certainly
some variants of it are. You are using 3.10.0 though which is nearly four years
old.

The 32 bit issue is almost certainly FreeBSD specific and should be reported to
the people maintaining the FreeBSD port which is out of tree and not maintained
by us.

-- 
You are receiving this mail because:
You are watching all bug changes.