On 29.03.2015 23:29, Davide Pesavento wrote:
On Sun, Mar 29, 2015 at 9:12 PM, Matthias Schwarzott z...@gentoo.org wrote:
On 29.03.2015 20:58, Matthias Schwarzott wrote:
Hi there!
I updated my ~amd64 system recently to new hardware (Intel Core i3-4160).
Since then valgrind did no longer work
Hi there!
I updated my ~amd64 system recently to new hardware (Intel Core i3-4160).
Since then valgrind did no longer work for 32bit programs because
-march=native did choose instructions that valgrind does not support
in 32bit mode (even ld.so was unusable).
After some research I put this into
On Sun, Mar 29, 2015 at 11:58 AM, Matthias Schwarzott z...@gentoo.org wrote:
Hi there!
I updated my ~amd64 system recently to new hardware (Intel Core i3-4160).
Since then valgrind did no longer work for 32bit programs because
-march=native did choose instructions that valgrind does not
On 29.03.2015 20:58, Matthias Schwarzott wrote:
Hi there!
I updated my ~amd64 system recently to new hardware (Intel Core i3-4160).
Since then valgrind did no longer work for 32bit programs because
-march=native did choose instructions that valgrind does not support
in 32bit mode (even
On 03/29/15 15:07, Matt Turner wrote:
On Sun, Mar 29, 2015 at 11:58 AM, Matthias Schwarzott z...@gentoo.org wrote:
Hi there!
I updated my ~amd64 system recently to new hardware (Intel Core i3-4160).
Since then valgrind did no longer work for 32bit programs because
-march=native did choose
On Sun, Mar 29, 2015 at 9:12 PM, Matthias Schwarzott z...@gentoo.org wrote:
On 29.03.2015 20:58, Matthias Schwarzott wrote:
Hi there!
I updated my ~amd64 system recently to new hardware (Intel Core i3-4160).
Since then valgrind did no longer work for 32bit programs because
-march=native did
