From: Feiyang C. <chr...@gm...> - 2024-09-20 05:04:59
|
Hi, I have rebased onto the latest commit and made some small fixes (the last two commits), but I'm uncertain about these fixes. https://github.com/FreeFlyingSheep/valgrind-loongarch64 The tests for close_range fail due to the if statement in POST(sys_close_range). - if (ARG2 == ~0U) + if ((UInt)ARG2 == ~0U) On LoongArch64/Linux, ARG2 is sign-extended, so I truncate it when comparing it to ~0U. The test for long_namespace_xml fails since Valgrind reports the following: Conditional jump or move depends on uninitialised value(s) at 0x40624F4: bcmp (vg_replace_strmem.c:1233) by 0x415E1DB: std::ctype<char>::_M_widen_init() const (in /usr/lib64/libstdc++.so.6.0.33) by 0x41D9067: std::basic_ostream<char, std::char_traits<char> >& std::endl<char, std::char_traits<char> >(std::basic_ostream<char, std::char_traits<char> >&) (in /usr/lib64/libstdc++.so.6.0.33) ... by 0x1200042BF: main (long_namespace_xml.cpp:45) I added a suppression for this issue. However, there are still two failures that I don't know how to solve. 1. The first one is pth_mutex_signal, which reports "The futex facility returned an unexpected error code." 2. The second one is libvexmultiarch_test, which causes an assertion failure in PPC: vex: priv/host_ppc_defs.c:4754(emit_PPCInstr): Assertion `delta >= 16 && delta <=32 && 0 == (delta & 3)' failed. //// failure exit called by libVEX I would appreciate your help with these issues and would like to know when you might be available to review my patches. Thanks, Feiyang |