Created attachment 298563 [details] emerge --info Valgrind is unusable, crashes with every binary. With dynamically linked binaries: vex amd64->IR: unhandled instruction bytes: 0xC5 0xF9 0xEF 0xC0 0xC7 0x5 0xF 0xAF ==16167== valgrind: Unrecognised instruction at address 0x4007e7b. ==16167== at 0x4007E7B: _dl_init_paths (in /lib64/ld-2.14.1.so) ==16167== by 0x4002D83: dl_main (in /lib64/ld-2.14.1.so) ==16167== by 0x401587D: _dl_sysdep_start (in /lib64/ld-2.14.1.so) ==16167== by 0x4004CB7: _dl_start (in /lib64/ld-2.14.1.so) ==16167== by 0x4000A87: ??? (in /lib64/ld-2.14.1.so) ...and compiled with -static: vex amd64->IR: unhandled instruction bytes: 0xC5 0xF9 0xEF 0xC0 0xC7 0x5 0x93 0x6B ==16356== valgrind: Unrecognised instruction at address 0x470377. ==16356== at 0x470377: _dl_init_paths (in /tmp/a.out) ==16356== by 0x44200A: _dl_non_dynamic_init (in /tmp/a.out) ==16356== by 0x442B13: __libc_init_first (in /tmp/a.out) ==16356== by 0x40DA44: (below main) (in /tmp/a.out) The instruction is: 470377: c5 f9 ef c0 vpxor %xmm0,%xmm0,%xmm0 System was compiled by gcc-4.5.3 with C{,XX}FLAGS -O2 -march=native on AMD FX. glibc version: GNU C Library stable release version 2.14.1, by Roland McGrath et al. (...) Compiled by GNU CC version 4.5.3. Compiled on a Linux 3.1.0 system on 2012-01-02. emerge --info attached
Had the same issue here on SandyBridge. Solution is simple: Wait for valgrind-devs to add AVX-support :/ Upstream Bug: https://bugs.kde.org/show_bug.cgi?id=273475 But since october there were no new commits to the AVX-branch, also in trunk I could not read something about AVX in the commit log.
(In reply to comment #1) > Had the same issue here on SandyBridge. > Solution is simple: Wait for valgrind-devs to add AVX-support :/ > Upstream Bug: https://bugs.kde.org/show_bug.cgi?id=273475 > But since october there were no new commits to the AVX-branch, also in trunk I > could not read something about AVX in the commit log. Franz! Thanks! You saved me some googling :) I attached a link on the upstream bug report back to this one to alert them.
AVX is now implemented and has moved into SVN. The slyfox overlay (in Layman) has a valgrind-9999 ebuild that works very well on Sandy Bridge here.
(In reply to comment #3) > AVX is now implemented and has moved into SVN. The slyfox overlay (in > Layman) has a valgrind-9999 ebuild that works very well on Sandy Bridge here. I prefer to wait until the next release. I know that people want this feature now, but using a prerelease can introduce as many headaches as new features.
(In reply to comment #4) > (In reply to comment #3) > > AVX is now implemented and has moved into SVN. The slyfox overlay (in > > Layman) has a valgrind-9999 ebuild that works very well on Sandy Bridge here. > > I prefer to wait until the next release. I know that people want this > feature now, but using a prerelease can introduce as many headaches as new > features. I only posted this for people who need it right now. I am unable to use Valgrind 3.7.0 on my system. It doesn't matter that I prefer to wait for the next release. I need Valgrind during development. Waiting is not an option, regardless of what I prefer.
Fixed with 3.8.0, right? The release notes say "Intel AVX and AES instructions are now supported."
Yes, 3.8.0 works fine here with AVX-enabled executables.
(In reply to comment #7) > Yes, 3.8.0 works fine here with AVX-enabled executables. Okay, I see no reason to backport. We're currently stabilizing 3.7.0 and I will soon start on 3.8.0. In the mean time, please use ~arch.
