[valgrind] [Bug 444781] MIPS: wrong syscall numbers used
https://bugs.kde.org/show_bug.cgi?id=444781 Petar Jovanovic changed: What|Removed |Added CC||mips3...@gmail.com Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Petar Jovanovic --- This issue has been fixed on the trunk. Relevant commits: commit efaa17e53a750d5f0f4c138b507b1b104729ed67 mips: skip using shared syscall numbers for mips64 commit 54d6ad3348fb50f5b972fe9c05d0d8757bfe73ba mips: skip using shared syscall numbers for mips32 Please reopen the issue if you see any problems. Thanks for reporting the problem and sending the patch. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 429350] vex mips->IR: unhandled instruction bytes: 0xB0 0xC4 0xB5 0x40
https://bugs.kde.org/show_bug.cgi?id=429350 Petar Jovanovic changed: What|Removed |Added CC||mips3...@gmail.com Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Petar Jovanovic --- It looks like you are trying to run a binary that has been compiled with -mips16. Valgrind does not support that. If you want to use Valgrind, please rebuild the software without mips16 flag. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 413547] regression test does not check for Arm 64 features
https://bugs.kde.org/show_bug.cgi?id=413547 Petar Jovanovic changed: What|Removed |Added CC||mips3...@gmail.com --- Comment #11 from Petar Jovanovic --- tests/arm64_features is built for each platform, but sys/auxv.h is not available everywhere and it will lead to build failure such as: arm64_features.c:5:22: fatal error: sys/auxv.h: No such file or directory compilation terminated. make[3]: *** [arm64_features.o] Error 1 Can we make this #include conditional? We can check for existence of getauxval(), or we may simply exclude it for non-arm builds with something like diff --git a/tests/arm64_features.c b/tests/arm64_features.c index 916a4e2..2c5670e 100644 --- a/tests/arm64_features.c +++ b/tests/arm64_features.c @@ -1,7 +1,7 @@ #include #include #include -#if !defined(__APPLE__) +#if !defined(__APPLE__) && defined(VGA_arm64) #include #endif -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 416285] Use prlimit64 in VG_(getrlimit) and VG_(setrlimit)
https://bugs.kde.org/show_bug.cgi?id=416285 Petar Jovanovic changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from Petar Jovanovic --- Committed. https://sourceware.org/git/?p=valgrind.git;a=commit;h=09f4f2f8fd9cdecb994e74df8b938108a01120f7 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417266] Make memcheck/tests/linux/sigqueue usable with musl
https://bugs.kde.org/show_bug.cgi?id=417266 Petar Jovanovic changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Petar Jovanovic --- Committed. https://sourceware.org/git/?p=valgrind.git;a=commit;h=b07722631ff47670fa193198f5f56a1b7582673b -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 400162] Patch: Guard against __GLIBC_PREREQ for musl libc
https://bugs.kde.org/show_bug.cgi?id=400162 Petar Jovanovic changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #7 from Petar Jovanovic --- Committed. https://sourceware.org/git/?p=valgrind.git;a=commit;h=702b1fe56f6dd61d0003457728702248f46c6dcc -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417266] Make memcheck/tests/linux/sigqueue usable with musl
https://bugs.kde.org/show_bug.cgi?id=417266 --- Comment #2 from Petar Jovanovic --- Everyone OK to submit this? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 416285] Use prlimit64 in VG_(getrlimit) and VG_(setrlimit)
https://bugs.kde.org/show_bug.cgi?id=416285 --- Comment #2 from Petar Jovanovic --- Anyone against this patch? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 400162] Patch: Guard against __GLIBC_PREREQ for musl libc
https://bugs.kde.org/show_bug.cgi?id=400162 --- Comment #5 from Petar Jovanovic --- Everyone OK to land this? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417238] Test memcheck/tests/vbit-test fails on mips64 BE
https://bugs.kde.org/show_bug.cgi?id=417238 Petar Jovanovic changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #6 from Petar Jovanovic --- Committed at https://sourceware.org/git/?p=valgrind.git;a=commit;h=93bb2da218a691532cd709b195b687e02ac0f1d2 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417187] [MIPS] Conditional branch problem since 'grail' changes
https://bugs.kde.org/show_bug.cgi?id=417187 Petar Jovanovic changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #22 from Petar Jovanovic --- The patches have been committed. Thanks everyone. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 416682] [MIPS-Linux] mmap failed under valgrind
https://bugs.kde.org/show_bug.cgi?id=416682 --- Comment #12 from Petar Jovanovic --- (In reply to Krishna from comment #10) > Created attachment 126722 [details] > mips mmap executable file This is not statically linked program. $ ldd mips_mmap_exe libssp.so.0 => not found libgcc_s.so.1 => /lib/mipsel-linux-gnu/libgcc_s.so.1 (0x7725) libc.so.0 => not found libc.so.6 => /lib/mipsel-linux-gnu/libc.so.6 (0x770b) /lib/ld-uClibc.so.0 => /lib/ld.so.1 (0x772b) Can you share the source code of this example and what toolchain to use, how to build it, so I can reproduce the issue? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 416682] [MIPS-Linux] mmap failed under valgrind
https://bugs.kde.org/show_bug.cgi?id=416682 --- Comment #9 from Petar Jovanovic --- @Krishna Can you share some steps to reproduce this issue? Can you come up with a small example, build it statically and upload the binary somewhere? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 415516] Can't cross compile on openwrt
https://bugs.kde.org/show_bug.cgi?id=415516 --- Comment #4 from Petar Jovanovic --- I would suggest that this issue gets resolved by upgrading toolchain version, if possible. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417187] [MIPS] Conditional branch problem since 'grail' changes
https://bugs.kde.org/show_bug.cgi?id=417187 Petar Jovanovic changed: What|Removed |Added CC||mips3...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 400872] Add nanoMIPS support to Valgrind
https://bugs.kde.org/show_bug.cgi?id=400872 Petar Jovanovic changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #25 from Petar Jovanovic --- Thank you for your contribution. There will likely be more changes and finetuning for nanomips, but this set of changes gets majority of support in place. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 400872] Add nanoMIPS support to Valgrind
https://bugs.kde.org/show_bug.cgi?id=400872 --- Comment #24 from Petar Jovanovic --- (In reply to Aleksandar Rikalo from comment #20) > Created attachment 124469 [details] > Add tests for nanoMIPS instruction set Committed https://sourceware.org/git/gitweb.cgi?p=valgrind.git;a=commit;h=9acc066ffcf37ad04edfc801cc610ae64fa8d771 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 400872] Add nanoMIPS support to Valgrind
https://bugs.kde.org/show_bug.cgi?id=400872 --- Comment #23 from Petar Jovanovic --- (In reply to Aleksandar Rikalo from comment #19) > Created attachment 124468 [details] > Fix some tests so they can be compiled for nanoMIPS Committed https://sourceware.org/git/gitweb.cgi?p=valgrind.git;a=commit;h=192c1673c75737c9ea6b5af7cfdc7b0681759933 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 400872] Add nanoMIPS support to Valgrind
https://bugs.kde.org/show_bug.cgi?id=400872 --- Comment #22 from Petar Jovanovic --- (In reply to Aleksandar Rikalo from comment #18) > Created attachment 124467 [details] > Add nanoMIPS support to Valgrind 4/4 Committed https://sourceware.org/git/gitweb.cgi?p=valgrind.git;a=commit;h=deae79f733a7c69f183f0e29a720e6c5bc3c1e7f -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 400872] Add nanoMIPS support to Valgrind
https://bugs.kde.org/show_bug.cgi?id=400872 Petar Jovanovic changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #21 from Petar Jovanovic --- (In reply to Aleksandar Rikalo from comment #17) > Created attachment 124466 [details] > Add nanoMIPS support to Valgrind 3/4 Committed https://sourceware.org/git/gitweb.cgi?p=valgrind.git;a=commit;h=24c1f4ada32ce119dd4b1149c44c5c3d4b7f9b38 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 414565] Specific use case bug found in SysRes VG_(do_sys_sigprocmask)
https://bugs.kde.org/show_bug.cgi?id=414565 Petar Jovanovic changed: What|Removed |Added CC||mips3...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 412344] Problem setting mips flags with specific paths
https://bugs.kde.org/show_bug.cgi?id=412344 Petar Jovanovic changed: What|Removed |Added Status|REPORTED|RESOLVED CC||mips3...@gmail.com Resolution|--- |FIXED --- Comment #4 from Petar Jovanovic --- Fixed in https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=8f6e97cf6544c5c83945caf01397ac265f6f055a Thanks Chris. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 400872] Add nanoMIPS support to Valgrind
https://bugs.kde.org/show_bug.cgi?id=400872 Petar Jovanovic changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #16 from Petar Jovanovic --- (In reply to Aleksandar Rikalo from comment #11) > Created attachment 122260 [details] > Add nanoMIPS support to Valgrind 2/4 First of all, thank you for all this work. I have committed majority of the changes from the patches #1 (VEX) and #2 (Coregrind). As I said in a different thread, I believe some parts of it can be omitted or done differently, so please revisit the changes that have not been applied and resend what you believe should still be committed and we can continue discussion from there. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 400593] In Coregrind, use statx for some internal syscalls if [f]stat[64] fail
https://bugs.kde.org/show_bug.cgi?id=400593 Petar Jovanovic changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #6 from Petar Jovanovic --- (In reply to Philippe Waroquiers from comment #5) > (In reply to Petar Jovanovic from comment #4) > > This version looks better, thanks. > > I have just pushed it [1] after some testing, but I will leave the issue > > open so we can see over the weekend whether there have been regressions on > > other platforms or not. > > > > [1] > > https://sourceware.org/git/?p=valgrind.git;a=commit; > > h=c6a6cf929f3e2a9bf5d7f09f334ed4d67f2d6e18 > > Would be good to add the bug nr in NEWS fixed list. > > Thanks Done. I just wanted to see results on the mailing list before add it to the NEWS. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 400593] In Coregrind, use statx for some internal syscalls if [f]stat[64] fail
https://bugs.kde.org/show_bug.cgi?id=400593 Petar Jovanovic changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #4 from Petar Jovanovic --- This version looks better, thanks. I have just pushed it [1] after some testing, but I will leave the issue open so we can see over the weekend whether there have been regressions on other platforms or not. [1] https://sourceware.org/git/?p=valgrind.git;a=commit;h=c6a6cf929f3e2a9bf5d7f09f334ed4d67f2d6e18 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 400872] Add nanoMIPS support to Valgrind
https://bugs.kde.org/show_bug.cgi?id=400872 --- Comment #9 from Petar Jovanovic --- (In reply to Aleksandar Rikalo from comment #1) > Created attachment 116206 [details] > Add nanoMIPS support to Valgrind 1/4 Can you rebase all the changes and make sure no new warnings are generated after the patches are applied? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 400593] In Coregrind, use statx for some internal syscalls if [f]stat[64] fail
https://bugs.kde.org/show_bug.cgi?id=400593 --- Comment #2 from Petar Jovanovic --- I can see new failures with the change applied: == 238 tests, 4 stderr failures, 4 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == none/tests/bigcode (stdout) none/tests/bigcode (stderr) none/tests/map_unmap (stdout) none/tests/map_unmap (stderr) none/tests/sigstackgrowth(stdout) none/tests/sigstackgrowth(stderr) none/tests/stackgrowth (stdout) none/tests/stackgrowth (stderr) arch: x86_64 glibc version: 2.27 I am getting these kind of errors: +--18001:0: aspacem segment mismatch: V's seg 1st, kernel's 2nd: +--18001:0: aspacem 1: file 108000-108fff4096 r-x-- SmFixed d=0x i=178667325 o=0 (1,64) /home/petarj/radni/valgrind/trunk/none/tests/sigstackgrowth +--18001:0: aspacem ...: 108000-108fff4096 r-x.. ... d=0x i=178667325 o=0 (.) m=. /home/petarj/radni/valgrind/trunk/none/tests/sigstackgrowth +--18001:0: aspacem sync check at m_aspacemgr/aspacemgr-linux.c:2053 (vgPlain_am_get_advisory): FAILED +--18001:0: aspacem +--18001:0: aspacem Valgrind: FATAL: aspacem assertion failed: +--18001:0: aspacem VG_(am_do_sync_check) (__PRETTY_FUNCTION__,__FILE__,__LINE__) +--18001:0: aspacem at m_aspacemgr/aspacemgr-linux.c:2053 (vgPlain_am_get_advisory) +--18001:0: aspacem Exiting now. According to the results on the valgrind-testresults mailing list, it seems these errors are already present on some arches and configurations. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 407557] Loongson specific instructions not implemented
https://bugs.kde.org/show_bug.cgi?id=407557 Petar Jovanovic changed: What|Removed |Added Summary|mips support problem on |Loongson specific |Loongson (mips64el) |instructions not ||implemented -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 407557] mips support problem on Loongson (mips64el)
https://bugs.kde.org/show_bug.cgi?id=407557 Petar Jovanovic changed: What|Removed |Added CC||mips3...@gmail.com --- Comment #2 from Petar Jovanovic --- I am not aware of anyone doing the work to support Loongson specific instructions. As I said on the mailing list, I suggest you install regular MIPS64 Debian, then it should work without problems. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 410599] Non-deterministic behaviour of pth_self_kill_15_other test
https://bugs.kde.org/show_bug.cgi?id=410599 Petar Jovanovic changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #6 from Petar Jovanovic --- Pushed. https://sourceware.org/git/?p=valgrind.git;a=commit;h=14911f7d6cc92df110c5987549bfcd84279009a5 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 410599] Non-deterministic behaviour of pth_self_kill_15_other test
https://bugs.kde.org/show_bug.cgi?id=410599 Petar Jovanovic changed: What|Removed |Added CC||philippe.waroquiers@skynet. ||be -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 400872] Add nanoMIPS support to Valgrind
https://bugs.kde.org/show_bug.cgi?id=400872 --- Comment #8 from Petar Jovanovic --- I will try to review and merge these changes hopefully soon. If anyone has any objections, please raise them here. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 400593] In Coregrind, use statx for some internal syscalls if [f]stat[64] fail
https://bugs.kde.org/show_bug.cgi?id=400593 --- Comment #1 from Petar Jovanovic --- Is everyone OK with this change? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 407218] Add support for the copy_file_range syscall
https://bugs.kde.org/show_bug.cgi?id=407218 --- Comment #5 from Petar Jovanovic --- (In reply to Mark Wielaard from comment #4) > > Does the following work on mips32? Yes, it does. Can you commit the change? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 406824] Unsupported baseline
https://bugs.kde.org/show_bug.cgi?id=406824 Petar Jovanovic changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #5 from Petar Jovanovic --- If there is a request to support Loongson specific instructions, please open a new ticket. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 406824] Unsupported baseline
https://bugs.kde.org/show_bug.cgi?id=406824 --- Comment #4 from Petar Jovanovic --- (In reply to Dapeng from comment #3) > it's worked, but new problem came out... > ==6577== > vex mips->IR: unhandled instruction bytes: 0x7C 0x19 0xB7 0xEB > ==6577== valgrind: Unrecognised instruction at address 0x4006abc. This is a different issue. The opcode says this is swc2: 0x0: swc2$23,6524(sp) but I believe Loongson-3 has overridden COP2 instruction formats. I suggest you install regular MIPS64 Debian, then it will work without problems. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 407218] Add support for the copy_file_range syscall
https://bugs.kde.org/show_bug.cgi?id=407218 --- Comment #3 from Petar Jovanovic --- (In reply to Mark Wielaard from comment #1) > Very nice. This looks good. (disclaimer, Sasha and I already did discuss > this patch on irc). I did two tweaks. Removed the args from vgtest file (the > testcase doesn't need arguments anymore). And added a NEWS entry/this bug > number (which is indeed kinda circular, you only know the bug number after > submitting the bug). > > commit 5f00db054a6f59502e9deeeb59ace2261207ee31 > Author: Alexandra Hajkova > Date: Thu May 2 08:24:02 2019 -0400 > > Add support for the copy_file_range syscall > > Support amd64, x86, arm64, ppc64, ppc32 and s390x architectures. > Also add sys-copy_file_range test case. > > I'll test on arm32. I believe the code should work as is there too. > > Petar, could you check whether mip32/mips64 can also be hooked up? Mark, the sys-copy_file_range.stderr.exp does not cover all the cases. Here is a exp diff on mips32: 5a6,10 > Syscall param copy_file_range(off_in) points to unaddressable byte(s) >... >by 0x: main (sys-copy_file_range.c:57) > Address 0x is not stack'd, malloc'd or (recently) free'd > 21c26 < ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0) --- > ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0) In short, on mips32 one more issue is reported. How do you want to handle this? New exp file or something else? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 406824] Unsupported baseline
https://bugs.kde.org/show_bug.cgi?id=406824 Petar Jovanovic changed: What|Removed |Added CC||mips3...@gmail.com Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Petar Jovanovic --- Fixed in a47a8b3e87590df048967574982d0a3db8f13450 [1]. [1] https://sourceware.org/git/?p=valgrind.git;a=commit;h=a47a8b3e87590df048967574982d0a3db8f13450 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 400975] Compile error: error: '-mips64r2' conflicts with the other architecture options, which specify a mips64 processor
https://bugs.kde.org/show_bug.cgi?id=400975 Petar Jovanovic changed: What|Removed |Added Status|RESOLVED|VERIFIED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 400164] helgrind test encounters mips x-compiler warnings and assembler error
https://bugs.kde.org/show_bug.cgi?id=400164 Petar Jovanovic changed: What|Removed |Added CC||mips3...@gmail.com Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Petar Jovanovic --- I hope this is fixed with https://sourceware.org/git/?p=valgrind.git;a=commit;h=d6da48fe5ac2e94fe28184ff334cd6b2283ef9a6 Randy, can you confirm? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 400975] Compile error: error: '-mips64r2' conflicts with the other architecture options, which specify a mips64 processor
https://bugs.kde.org/show_bug.cgi?id=400975 Petar Jovanovic changed: What|Removed |Added CC||mips3...@gmail.com Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Petar Jovanovic --- I hope this is fixed with https://sourceware.org/git/?p=valgrind.git;a=commit;h=e61d13087096139024788393218367572751b4b6 Peter, can you check with Valgrind ToT? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 402123] invalid assembler opcodes for mips32r2
https://bugs.kde.org/show_bug.cgi?id=402123 Petar Jovanovic changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from Petar Jovanovic --- (In reply to Julian Seward from comment #3) > Petar, any idea about this? I hope this is fixed with https://sourceware.org/git/?p=valgrind.git;a=commit;h=e61d13087096139024788393218367572751b4b6 cote2004-github, can you check with Valgrind ToT? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405430] Use gcc -Wimplicit-fallthrough=2 by default if available
https://bugs.kde.org/show_bug.cgi?id=405430
--- Comment #3 from Petar Jovanovic ---
(In reply to Mark Wielaard from comment #0)
> I would like to enable -Wimplicit-fallthrough=2 by default when available.
> It was introduced in GCC7. It caught a couple of bugs, but it does need a
> bit of extra comments to explain when a switch case statement fall-through
> is deliberate. Luckily with -Wimplicit-fallthrough=2 various existing
> comments already do that. I have fixed the bugs, but adding explicit break
> statements where necessary and added comments where the fall-through was
> correct.
>
> There is just one place that produces a warning for a fallthrough that I am
> not sure is deliberate or not.
>
> priv/guest_mips_toIR.c: In function ‘disInstr_MIPS_WRK’:
> priv/guest_mips_toIR.c:30205:13: warning: this statement may fall through
> [-Wimplicit-fallthrough=]
> if (VEX_MIPS_COMP_ID(archinfo->hwcaps) == VEX_PRID_COMP_CAVIUM) {
> ^
> priv/guest_mips_toIR.c:30211:7: note: here
>case 0xC: /* INSV */
>^~~~
This fallthrough is deliberate. I have made a comment in the git log to state
this.
Otherwise, changes in MIPS files look good to me. Thanks.
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 405458] MIPS mkFormVEC arguments swapped?
https://bugs.kde.org/show_bug.cgi?id=405458 Petar Jovanovic changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Petar Jovanovic --- Well spotted. Fixed in: https://sourceware.org/git/?p=valgrind.git;a=commit;h=029f1196fcafb49183c87c53e3a7febc762a0dc8 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 402351] mips64 libvexmultiarch_test fails on s390x
https://bugs.kde.org/show_bug.cgi?id=402351 Petar Jovanovic changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #7 from Petar Jovanovic --- Fixed with https://sourceware.org/git/?p=valgrind.git;a=commit;h=cd20c8ca5815f0abf9d1bdb47888753bdb5c5738 Sorry for a delay in taking a look at this. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 402351] mips64 libvexmultiarch_test fails on s390x
https://bugs.kde.org/show_bug.cgi?id=402351 Petar Jovanovic changed: What|Removed |Added Assignee|jsew...@acm.org |mips3...@gmail.com Status|CONFIRMED |ASSIGNED --- Comment #6 from Petar Jovanovic --- This problem is triggered when VEX is configured for MIPS64 w/ 32-bit FPUs. Since this can happen only in artificial cases, I will go with adjusting the test itself. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 402351] mips64 libvexmultiarch_test fails on s390x
https://bugs.kde.org/show_bug.cgi?id=402351 --- Comment #2 from Petar Jovanovic --- I will take a look at it. Is there a way to reproduce it myself? I am not seeing any s390 boards on GCC farm unfortunately. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 342356] MIPS: determine page size at runtime
https://bugs.kde.org/show_bug.cgi?id=342356 Petar Jovanovic changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #6 from Petar Jovanovic --- Fixed in r15813. Closing it. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 338924] mips: wrong instruction emitted
https://bugs.kde.org/show_bug.cgi?id=338924 Petar Jovanovic changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #3 from Petar Jovanovic --- Fixed long time ago. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 328441] valgrind_3.9.0 failed to compile in mips32 “Error: illegal operands `cfc1 $t0,$31'”
https://bugs.kde.org/show_bug.cgi?id=328441 Petar Jovanovic changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED --- Comment #6 from Petar Jovanovic --- No updates or new info for 4 years. Closing it. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 328147] vex mips->IR: unhandled instruction bytes: 0x0 0x0 0x0 0xE
https://bugs.kde.org/show_bug.cgi?id=328147 Petar Jovanovic changed: What|Removed |Added Resolution|WAITINGFORINFO |UNMAINTAINED Status|NEEDSINFO |RESOLVED --- Comment #10 from Petar Jovanovic --- No updates or new info for 4 years. Closing it. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 373069] memcheck/tests/leak_cpp_interior fails with GCC 5.1+
https://bugs.kde.org/show_bug.cgi?id=373069 Petar Jovanovic changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #6 from Petar Jovanovic --- Closing this as (partially) fixed. For the remaining part of the problem, check https://bugs.kde.org/show_bug.cgi?id=345307. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 396905] compile tests failure on mips32-linux: Error: opcode not supported on this processor: mips1 (mips1)
https://bugs.kde.org/show_bug.cgi?id=396905 Petar Jovanovic changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #5 from Petar Jovanovic --- Closing this as "WORKSFORME". Reopen this issue if you are still having problems. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 328147] vex mips->IR: unhandled instruction bytes: 0x0 0x0 0x0 0xE
https://bugs.kde.org/show_bug.cgi?id=328147 --- Comment #9 from Petar Jovanovic --- Any update here? Otherwise, the issue will be closed. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 396905] compile tests failure on mips32-linux: Error: opcode not supported on this processor: mips1 (mips1)
https://bugs.kde.org/show_bug.cgi?id=396905 Petar Jovanovic changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #4 from Petar Jovanovic --- Changing status to NEEDSINFO. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 396906] compile tests failure on mips32-linux: broken inline asm in tests on mips32-linux
https://bugs.kde.org/show_bug.cgi?id=396906 Petar Jovanovic changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Petar Jovanovic --- Committed. Thank you for the patch. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 396905] compile tests failure on mips32-linux: Error: opcode not supported on this processor: mips1 (mips1)
https://bugs.kde.org/show_bug.cgi?id=396905 --- Comment #3 from Petar Jovanovic --- Does Aleksandar's comment and suggestion work for you? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 397424] glibc 2.27 and gdb_server tests
https://bugs.kde.org/show_bug.cgi?id=397424 Petar Jovanovic changed: What|Removed |Added CC||philippe.waroquiers@skynet. ||be Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Petar Jovanovic --- I can confirm that we have 4 failurs in gdbserver_tests on x86 with 2.27 glibc. == 26 tests, 1 stderr failure, 0 stdout failures, 1 stderrB failure, 2 stdoutB failures, 0 post failures == gdbserver_tests/mcinfcallWSRU(stderrB) gdbserver_tests/mcmain_pic (stderr) gdbserver_tests/nlcontrolc (stdoutB) gdbserver_tests/nlvgdbsigqueue (stdoutB) After appling the patch, we have issue remaining. -- Finished tests in gdbserver_tests --- == 26 tests, 1 stderr failure, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == gdbserver_tests/mcmain_pic (stderr) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 382563] MIPS MSA ASE support
https://bugs.kde.org/show_bug.cgi?id=382563 Petar Jovanovic changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #21 from Petar Jovanovic --- (In reply to Julian Seward from comment #20) > Petar, can this be closed now? Yes, it can. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 345763] MIPS N32 ABI support
https://bugs.kde.org/show_bug.cgi?id=345763 Petar Jovanovic changed: What|Removed |Added Assignee|jsew...@acm.org |mips3...@gmail.com Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #38 from Petar Jovanovic --- Support for N32 ABI has finally landed in a series of 4 patches: #1 additional use of RegWord https://sourceware.org/git/?p=valgrind.git;a=commit;h=8b2fe98aca7568a821c921ba3183f7d62b35a12c #2 mips64: use RegWord where appplicable https://sourceware.org/git/?p=valgrind.git;a=commit;h=ac58a6b8578697bdbfdfdcc8d2c70f8f93eef8c0 #3 mips64: add N32 ABI support https://sourceware.org/git/?p=valgrind.git;a=commit;h=9a6cf7a41c7e7a32e0d0a369b4519b97e2569d3d #4 mips64: update tests for N32 ABI https://sourceware.org/git/?p=valgrind.git;a=commit;h=58c1c98db4eb8a66ddea228ab00c8ac1bd7e027c Please test it now on your machines. Thanks for the contribution. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 387410] MIPSr6 support
https://bugs.kde.org/show_bug.cgi?id=387410 --- Comment #5 from Petar Jovanovic --- The patches have been committed to the trunk. Thanks for the great work. This issue can be closed now. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 320546] valgrind exits with "Assertion 'in_rx' failed" for /system/lib/libva-android.so on Android 4.0.4
https://bugs.kde.org/show_bug.cgi?id=320546 Petar Jovanovic changed: What|Removed |Added CC||mips3...@gmail.com --- Comment #2 from Petar Jovanovic --- There is a patch [1] on the master branch that fixes an issue that looks similar to this one. Can you try to build Valgrind ToT and test it with your application? [1] https://sourceware.org/git/?p=valgrind.git;a=commit;h=0eea388934a228231843d8c13cfd99bb170074f1 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 382563] MIPS MSA ASE support
https://bugs.kde.org/show_bug.cgi?id=382563 --- Comment #19 from Petar Jovanovic --- I have committed the changes. Minor code-style issues have been fixed, but generally, this is great work, thank you for contributing it. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 382563] MIPS MSA ASE support
https://bugs.kde.org/show_bug.cgi?id=382563 --- Comment #11 from Petar Jovanovic --- (In reply to Tamara Vlahovic from comment #8) > Created attachment 107721 [details] > mips_msa_03 - Implementation of MSA ASE for VEX. > Can you please do some refactoring of this patch in a way that you do not have very large functions, most particularly disMSAInstr_MIPS_WRK? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 381553] VEX register allocator v3
https://bugs.kde.org/show_bug.cgi?id=381553 --- Comment #69 from Petar Jovanovic --- (In reply to Ivo Raisr from comment #68) > If I understand your comment correctly, you are saying that MIPS front end > misuses DivModU128to64 for something which is not intended. Yes, instead of using (nonexistent) Iop_DivModU64to64, it uses DivModU128to64 but the back'end implements simplified code it as it was Iop_DivModU64to64. It will be fixed. > Then please go ahead and fix that but please do not associate it in any way > with this bug > as these are independent. Don't worry. :) I just put explanation here of the dead code issue here. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 381553] VEX register allocator v3
https://bugs.kde.org/show_bug.cgi?id=381553 --- Comment #67 from Petar Jovanovic --- (In reply to Ivo Raisr from comment #65) > (In reply to Petar Jovanovic from comment #63) > > > The latest patch (lucky 13) seems to work fine on one MIPS variant I > > have tested. Thanks for the extra work. > > I will test other MIPS variants early next week. > > Petar, thank you for the testing so far. Have you had a chance to test other > MIPS variants? Yes, I can confirm now that v13 has been tested on other MIPS variants and it is good to go. (In reply to Ivo Raisr from comment #62) > Also I think that this scenario happened because MIPS isel backend generated > dead code. You can discover more if you run the program with patches 012 and > options such as --trace-flags=1110 --trace-notbelow=0 and let the > program crash as before. Then please attach debug output of only the last SB. This seems to be related to the way how MIPS port uses and handles DivModU128to64 and some other Iops. The issue comes from tricks done due to the lack of appropriate Iops that I am considering to add now. These would be: Iop_DivModU64to64, // :: I64,I64 -> I128 // of which lo half is div and hi half is mod Iop_DivModS32to32, // :: I32,I32 -> I64 // of which lo half is div and hi half is mod Iop_DivModU32to32, // :: I32,I32 -> I64 // of which lo half is div and hi half is mod Does anyone object or is there a need to create a separate issue for it? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 381553] VEX register allocator v3
https://bugs.kde.org/show_bug.cgi?id=381553 --- Comment #63 from Petar Jovanovic --- (In reply to Ivo Raisr from comment #62) > Petar, please could you test please? > The latest patch (lucky 13) seems to work fine on one MIPS variant I have tested. Thanks for the extra work. I will test other MIPS variants early next week. > Also I think that this scenario happened because MIPS isel backend generated > dead code. You can discover more if you run the program with patches 012 and > options such as --trace-flags=1110 --trace-notbelow=0 and let the > program crash as before. Then please attach debug output of only the last SB. Thanks. Will look into it. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 381553] VEX register allocator v3
https://bugs.kde.org/show_bug.cgi?id=381553 --- Comment #58 from Petar Jovanovic --- Ivo, here is a new log. https://transfer.pcloud.com/download.html?code=5ZbBWcZMexCPcqqmR4ZFfeRZT410zHsBPVS9h74eABPRb4ByVQIX I could not attach it as it is too big, even after compression. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 382563] MIPS MSA ASE support
https://bugs.kde.org/show_bug.cgi?id=382563 Petar Jovanovic changed: What|Removed |Added CC||jsew...@acm.org --- Comment #6 from Petar Jovanovic --- (In reply to Tamara Vlahovic from comment #0) > Introduces new Iops in VEX necessary for implementing > some MSA V128 operations: >Iop_Scale2_32Fx4, Iop_Scale2_64Fx2, >Iop_Log2_32Fx4, Iop_Log2_64Fx2, >Iop_F32x4_2toQ16x8, Iop_F64x2_2toQ32x4, >Iop_PackOddLanes8x16, Iop_PackEvenLanes8x16, >Iop_PackOddLanes16x8, Iop_PackEvenLanes16x8, >Iop_PackOddLanes32x4, Iop_PackEvenLanes32x4. Julian, can you take a look at these? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 381553] VEX register allocator v3
https://bugs.kde.org/show_bug.cgi?id=381553 --- Comment #56 from Petar Jovanovic --- Situation is better, yet not ideal. Majority of the programs pass, but some crash. E.g. ~/radni/valgrind/trunk$ ./vg-in-place -q --track-origins=yes --vex-regalloc-version=3 ./memcheck/tests/atomic_incs vex: priv/host_generic_reg_alloc3.c:250 (spill_vreg): Assertion `vreg_state[v_idx].dead_before > (Short) current_ii' failed. vex storage: T total 55230600 bytes allocated vex storage: P total 0 bytes allocated valgrind: the 'impossible' happened: LibVEX called failure_exit(). host stacktrace: ==19301==at 0x58082A60: show_sched_status_wrk (m_libcassert.c:355) ==19301==by 0x58082C10: report_and_quit (m_libcassert.c:426) ==19301==by 0x58082E74: panic (m_libcassert.c:502) ==19301==by 0x58082E74: vgPlain_core_panic_at (m_libcassert.c:507) ==19301==by 0x58082EB8: vgPlain_core_panic (m_libcassert.c:512) ==19301==by 0x580A53B8: failure_exit (m_translate.c:740) ==19301==by 0x5817C9C0: vex_assert_fail (main_util.c:247) ==19301==by 0x58037790: spill_vreg (host_generic_reg_alloc3.c:250) ==19301==by 0x581C1ACC: doRegisterAllocation_v3 (host_generic_reg_alloc3.c:1048) ==19301==by 0x5817B310: libvex_BackEnd (main_main.c:1095) ==19301==by 0x5817B310: LibVEX_Translate (main_main.c:1198) ==19301==by 0x580A7E54: vgPlain_translate (m_translate.c:1794) ==19301==by 0x580EBBF4: handle_chain_me (scheduler.c:1084) ==19301==by 0x580EDDA4: vgPlain_scheduler (scheduler.c:1428) ==19301==by 0x581028F4: thread_wrapper (syswrap-linux.c:103) ==19301==by 0x581028F4: run_a_thread_NORETURN (syswrap-linux.c:156) sched status: running_tid=1 Thread 1: status = VgTs_Runnable (lwpid 19301) ==19301==at 0x4017228: _dl_determine_tlsoffset (dl-tls.c:239) ==19301==by 0x4002268: init_tls (rtld.c:615) ==19301==by 0x400492C: dl_main (rtld.c:1685) ==19301==by 0x401C240: _dl_sysdep_start (dl-sysdep.c:249) ==19301==by 0x4006220: _dl_start_final (rtld.c:307) ==19301==by 0x4006528: _dl_start (rtld.c:415) ==19301==by 0x40023CC: __start (in /lib/mips64el-linux-gnuabi64/ld-2.24.so) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 381553] VEX register allocator v3
https://bugs.kde.org/show_bug.cgi?id=381553 Petar Jovanovic changed: What|Removed |Added Attachment #107010|0 |1 is obsolete|| --- Comment #51 from Petar Jovanovic --- Created attachment 107011 --> https://bugs.kde.org/attachment.cgi?id=107011&action=edit log of MIPS execution (large) Here is the log, compressed. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 381553] VEX register allocator v3
https://bugs.kde.org/show_bug.cgi?id=381553 --- Comment #49 from Petar Jovanovic --- (In reply to Ivo Raisr from comment #43) > Petar, thank you for testing the patches. > Please could you test again with the latest patch called > "patch 010 - VEX part + some debugging for MIPS crashes". > It should print a bunch of debugging statements and then I hope to see what > went wrong there. Check the log in the comment #48. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 381553] VEX register allocator v3
https://bugs.kde.org/show_bug.cgi?id=381553 --- Comment #48 from Petar Jovanovic --- Created attachment 107010 --> https://bugs.kde.org/attachment.cgi?id=107010&action=edit log of MIPS execution -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 381553] VEX register allocator v3
https://bugs.kde.org/show_bug.cgi?id=381553 Petar Jovanovic changed: What|Removed |Added CC||mips3...@gmail.com --- Comment #41 from Petar Jovanovic --- With the changes (patch 010 Valgrind/VEX) applied, Memcheck is crashing on MIPS32/MIPS64. $ ./vg-in-place ls ==27412== Memcheck, a memory error detector ==27412== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==27412== Using Valgrind-3.14.0.SVN and LibVEX; rerun with -h for copyright info ==27412== Command: ls ==27412== vex: priv/host_generic_reg_alloc3.c:374 (find_free_rreg): Assertion `0' failed. vex storage: T total 2656776 bytes allocated vex storage: P total 0 bytes allocated valgrind: the 'impossible' happened: LibVEX called failure_exit(). host stacktrace: ==27412==at 0x580829C0: show_sched_status_wrk (m_libcassert.c:355) ==27412==by 0x58082B70: report_and_quit (m_libcassert.c:426) ==27412==by 0x58082DD4: panic (m_libcassert.c:502) ==27412==by 0x58082DD4: vgPlain_core_panic_at (m_libcassert.c:507) ==27412==by 0x58082E18: vgPlain_core_panic (m_libcassert.c:512) ==27412==by 0x580A5268: failure_exit (m_translate.c:740) ==27412==by 0x5817C720: vex_assert_fail (main_util.c:247) ==27412==by 0x580378D0: find_free_rreg.isra.2.constprop.8 (host_generic_reg_alloc3.c:374) ==27412==by 0x581BF13C: doRegisterAllocation (host_generic_reg_alloc3.c:917) ==27412==by 0x5817B0A4: libvex_BackEnd (main_main.c:1086) ==27412==by 0x5817B0A4: LibVEX_Translate (main_main.c:1185) ==27412==by 0x580A7D04: vgPlain_translate (m_translate.c:1794) ==27412==by 0x580EB9F4: handle_chain_me (scheduler.c:1084) ==27412==by 0x580EDBA4: vgPlain_scheduler (scheduler.c:1428) ==27412==by 0x581026F4: thread_wrapper (syswrap-linux.c:103) ==27412==by 0x581026F4: run_a_thread_NORETURN (syswrap-linux.c:156) sched status: running_tid=1 Thread 1: status = VgTs_Runnable (lwpid 27412) ==27412==at 0x400617C: _dl_start_final (rtld.c:281) ==27412==by 0x4006528: _dl_start (rtld.c:415) ==27412==by 0x40023CC: __start (in /lib/mips64el-linux-gnuabi64/ld-2.24.so) Note: see also the FAQ in the source distribution. It contains workarounds to several common problems. In particular, if Valgrind aborted or crashed after identifying problems in your program, there's a good chance that fixing those problems will prevent Valgrind aborting or crashing, especially if it happened in m_mallocfree.c. If that doesn't help, please report this bug to: www.valgrind.org In the bug report, send all the above text, the valgrind version, and what OS and version you are using. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 379473] MIPS: add support for rdhwr cycle counter register
https://bugs.kde.org/show_bug.cgi?id=379473 Petar Jovanovic changed: What|Removed |Added CC||mips3...@gmail.com --- Comment #1 from Petar Jovanovic --- Fixed in VEX r3362. Please retest with ToT code. Thanks for reporting the issue. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 321836] valgrind cross compilation failure on Ubuntu machine
https://bugs.kde.org/show_bug.cgi?id=321836 Petar Jovanovic changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #6 from Petar Jovanovic --- I believe this issue has been fixed in r14484. Please reopen the issue if there are more issues with the current trunk. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 331126] Compiling with mipsbe toolchain
https://bugs.kde.org/show_bug.cgi?id=331126 --- Comment #10 from Petar Jovanovic --- This issue should be closed. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 334649] [Cavium Octeon 2 MIPS64] valgrind is up but ld.so assert "rtld.c: 1257: dl_main: Assertion `_rtld_local._dl_rtld_map.l_relocated' failed" and exits
https://bugs.kde.org/show_bug.cgi?id=334649 --- Comment #7 from Petar Jovanovic --- As there have been no updates to this issue for years now, I think we should close it. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 334649] [Cavium Octeon 2 MIPS64] valgrind is up but ld.so assert "rtld.c: 1257: dl_main: Assertion `_rtld_local._dl_rtld_map.l_relocated' failed" and exits
https://bugs.kde.org/show_bug.cgi?id=334649 --- Comment #6 from Petar Jovanovic --- Any update here, Vien? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 359202] Add musl libc configure/compile
https://bugs.kde.org/show_bug.cgi?id=359202 --- Comment #7 from Petar Jovanovic --- This issue can be closed now. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 359202] Add musl libc configure/compile
https://bugs.kde.org/show_bug.cgi?id=359202 --- Comment #6 from Petar Jovanovic --- Committed as r16296. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 359202] Add musl libc configure/compile
https://bugs.kde.org/show_bug.cgi?id=359202 Petar Jovanovic changed: What|Removed |Added CC||mips3...@gmail.com --- Comment #4 from Petar Jovanovic --- (In reply to Peter Seiderer from comment #2) > Created attachment 97156 [details] > [PATCH v2] Fixes for musl libc. > > - add musl libc detection (prevents configure error) > - adjust preload and symbol names (based on the OpenWrt > patch, see [1]) > > [1] > https://dev.openwrt.org/browser/trunk/package/devel/valgrind/patches/200- > musl_fix.patch?rev=46302 > > Changes v1 -> v2: > change ifdef logic, fix uClibc spelling The patch makes sense. Anyone has objections that we put this into the tree? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 348924] MIPS: Load doubles through memory so the code compiles with the FPXX ABI
https://bugs.kde.org/show_bug.cgi?id=348924 --- Comment #6 from Petar Jovanovic --- (In reply to Ivo Raisr from comment #5) > I was not able to find any NEWS entry. > Will you add this to the list of bugs fixed in 3.12 release? I have just done that, thanks for a reminder. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 340777] Illegal instruction on mips (ar71xx)
https://bugs.kde.org/show_bug.cgi?id=340777 --- Comment #18 from Petar Jovanovic --- (In reply to Luiz Angelo De Luca from comment #17) > I switched to a new git mirror source. > > valgrind works like a charm with trunk@16292. Thank you very much. > Glad to hear so. > Would it take too long to get a new valgrind released? If not, I'll not > bother to backport to previous valgrind package. There is a discussion about new release, possibly in May: https://sourceforge.net/p/valgrind/mailman/message/35756720/ -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 340777] Illegal instruction on mips (ar71xx)
https://bugs.kde.org/show_bug.cgi?id=340777 --- Comment #16 from Petar Jovanovic --- (In reply to Luiz Angelo De Luca from comment #15) > root@router.lan3:/usr/bin# valgrind --version > valgrind-3.13.0.SVN > > The test was using commit svn://svn.valgrind.org/valgrind/trunk@16225 > a5019735-40e9-0310-863c-91ae7b9d1cf9 That I got from > https://github.com/liquid-mirror/valgrind. Is it recent enough? > No, it is not recent enough. Please take the latest SVN (better option) or cherry pick the change r16261. Let us know the behaviour of Valgrind after that. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 340777] Illegal instruction on mips (ar71xx)
https://bugs.kde.org/show_bug.cgi?id=340777 --- Comment #14 from Petar Jovanovic --- Luiz, any update? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 340777] Illegal instruction on mips (ar71xx)
https://bugs.kde.org/show_bug.cgi?id=340777 --- Comment #13 from Petar Jovanovic --- We are not able to reproduce this issue on our board with OpenWRT. Can you confirm that you have tried running the latest SVN version of Valgrind WITH the patch for MUSL (https://bugs.kde.org/show_bug.cgi?id=359202#c2) applied on the top of it? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 340777] Illegal instruction on mips (ar71xx)
https://bugs.kde.org/show_bug.cgi?id=340777 --- Comment #11 from Petar Jovanovic --- (In reply to Luiz Angelo De Luca from comment #10) > Here is where I get the SIGSEGV. Maybe stack got corrupted. Is there any > tips from here? Receiving some of these signals in GDB is an expected behaviour. Can you pass the following lines to gbd and rerun the executable? set heuristic-fence-post 99 handle SIGSEGV noprint nostop pass Keep running (w/ "continue") GDB until it fails. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 340777] Illegal instruction on mips (ar71xx)
https://bugs.kde.org/show_bug.cgi?id=340777 --- Comment #9 from Petar Jovanovic --- I believe the new (non-mips16) issues are not MIPS-related, but rather MUSL-related. Can you try to apply the patch in the second comment Bug 359202 and see if it sorts out your issues with binaries that do not have or use mips16 code? https://bugs.kde.org/show_bug.cgi?id=359202#c2 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 336768] vex mips->IR: unhandled instruction bytes: 0x3B 0xE8 0x3 0xEC
https://bugs.kde.org/show_bug.cgi?id=336768 --- Comment #24 from Petar Jovanovic --- I believe the issue was fixed by people applying locally the patch from the comment #3. This has not been upstreamed as it seems applicable only for the old BRCM systems, when their kernel did not use to publish full company name in the "cpu model" section. The problem itself is also, I believe, related to a very weird proprietary encoding of RDHWR instruction that is not in use on Broadcom systems anymore. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 336768] vex mips->IR: unhandled instruction bytes: 0x3B 0xE8 0x3 0xEC
https://bugs.kde.org/show_bug.cgi?id=336768 --- Comment #23 from Petar Jovanovic --- (In reply to Ivo Raisr from comment #22) > I was not able to find what is the status of this bug. Not sure either, but it seems that no one is complaining on this matter anymore. It has been more than 2 years since the last response, and the last comment was "it seems that your patch fix the problem! Thanks!" So, I would close this issue if there is no one to claim a problem. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 340777] Illegal instruction on mips (ar71xx)
https://bugs.kde.org/show_bug.cgi?id=340777 --- Comment #6 from Petar Jovanovic --- (In reply to Luiz Angelo De Luca from comment #5) >==24067== Illegal opcode at address 0x4077B5 >==24067==at 0x4077B5: ??? (in /bin/busybox) This looks suspicious. Is that busybox that has been compiled with -mips16 option? Note that Valgrind does not support mips16 for the time being. Can you do 'readelf -h /bin/busybox' and show us the output? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 340777] Illegal instruction on mips (ar71xx)
https://bugs.kde.org/show_bug.cgi?id=340777 --- Comment #4 from Petar Jovanovic --- Is this issue still valid? Are you seeing the issue with the latest Valgrind SVN code? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 336768] vex mips->IR: unhandled instruction bytes: 0x3B 0xE8 0x3 0xEC
https://bugs.kde.org/show_bug.cgi?id=336768 --- Comment #21 from Petar Jovanovic --- This issue should be closed. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 348924] MIPS: Load doubles through memory so the code compiles with the FPXX ABI
https://bugs.kde.org/show_bug.cgi?id=348924 --- Comment #4 from Petar Jovanovic --- This issue should be closed now. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 351692] Dumps created by valgrind are not readable by gdb
https://bugs.kde.org/show_bug.cgi?id=351692 --- Comment #3 from Petar Jovanovic --- This issue should be closed now. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 377376] memcheck/tests/linux/getregset fails with glibc2.24
https://bugs.kde.org/show_bug.cgi?id=377376 --- Comment #10 from Petar Jovanovic --- I have committed the build fix as r16275. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 377376] memcheck/tests/linux/getregset fails with glibc2.24
https://bugs.kde.org/show_bug.cgi?id=377376 --- Comment #7 from Petar Jovanovic --- (In reply to Aleksandra Karadzic from comment #2) > Created attachment 104456 [details] > Fix ptrace(traceme) The patch committed in r16273. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 375806] Test helgrind/tests/tc22_exit_w_lock fails with glibc 2.24
https://bugs.kde.org/show_bug.cgi?id=375806 --- Comment #3 from Petar Jovanovic --- This issue should be closed now. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 376142] Segfaults on MIPS Cavium Octeon boards
https://bugs.kde.org/show_bug.cgi?id=376142 --- Comment #6 from Petar Jovanovic --- (In reply to James Cowgill from comment #5) > Using the latest SVN does fix the hangs on Octeon. Also, I didn't know that > valgrind raised SIGSEGV during normal execution - indeed running 'continue' > in GDB does allow it to continue without error. Thanks! Great. We should close this issue now. -- You are receiving this mail because: You are watching all bug changes.
