https://bugs.kde.org/show_bug.cgi?id=407218
--- Comment #3 from Petar Jovanovic <mips3...@gmail.com> --- (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 <ahajk...@redhat.com> > 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.
