https://bugs.kde.org/show_bug.cgi?id=483711
Mark Wielaard <m...@klomp.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |m...@klomp.org
--- Comment #5 from Mark Wielaard <m...@klomp.org> ---
Various x86_64 (amd64) builders on builder.sourceware.org are docker based. I
think valgrind works fine under a linux container/docker setup. But none of
them run x86 (32bit).
The comments around the assert read:
case VG_TRC_INVARIANT_FAILED:
/* This typically happens if, after running generated code,
it is detected that host CPU settings (eg, FPU/Vector
control words) are not as they should be. Vex's code
generation specifies the state such control words should
be in on entry to Vex-generated code, and they should be
unchanged on exit from it. Failure of this assertion
usually means a bug in Vex's code generation. */
//{ UInt xx;
// __asm__ __volatile__ (
// "\t.word 0xEEF12A10\n" // fmrx r2,fpscr
// "\tmov %0, r2" : "=r"(xx) : : "r2" );
// VG_(printf)("QQQQ new fpscr = %08x\n", xx);
//}
vg_assert2(0, "VG_(scheduler), phase 3: "
"run_innerloop detected host "
"state invariant failure", trc);
--
You are receiving this mail because:
You are watching all bug changes.
