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 choose instructions that valgrind does not support
>> in 32bit mode (even ld.so was unusable).
>>
>> After some research I put this into make.conf and now it works:
>> CFLAGS_x86="${CFLAGS_x86} -mno-avx2 -mno-sse4 -mno-bmi -mno-bmi2"
>> CXXFLAGS_x86="${CXXFLAGS_x86} -mno-avx2 -mno-sse4 -mno-bmi -mno-bmi2"
>>
>> Is this the best solution to the problem?
>> If yes, the valgrind ebuild could suggest something like this.
>> Either always show it or check cpu-flags first (is this maintainable?).
>>
> I should add, that it seems to break for exactly one package: mariadb
>Not only mariadb, there are other known breakages... see https://bugs.gentoo.org/show_bug.cgi?id=541616#c5 According to mgorny (Cc'ed): "You are not supposed to touch CFLAGS_x86, ever. That's some magic stuff that's used in profiles & multilib.eclass." Regards, Davide
