> I'll shortly send a second message listing the bugs I think are a priority.
Please feel free to disagree and/or add other bugs. This is only my personal
prioritisation.
J
Higher prio (really should fix for 3.15.0)
404843 s390x: backtrace sometimes ends prematurely
405182 Valgrind fails to build with Clang
398183 (amd64) Vex errors with _mm256_shuffle_epi8/vpshufb
Potentially serious?
399287 (amd64) Illegal Instruction vcmptrueps
404272 vex amd64->IR: 0x66 0xF 0x38 0x23 0xC0 0xF3 (PMOVSXWD)
Should fix
400099 Memcheck produces truncated backtrace when len(argv + env) = 4096
Possible stack overrun problem; should investigate
n-i-bz (amd64) Support RDRAND/RDSEED ? We really should.
Medium prio (would be nice to fix for 3.15.0)
399355 Add callgrind_diff
400793 pthread_rwlock_timedwrlock false positive
Probably would be easy to fix, but requires testing
401284 False positive "Source and destination overlap in strncat"
possibly valid; possible off-by-one error in overlap checking?
405201 Incorrect size of struct vki_siginfo on 64-bit Linux architectures
400162 Patch: Guard against __GLIBC_PREREQ for musl libc
Looks like simple fix; should take
398870 (amd64) Please add support for instruction vcvtps2ph
400538 vex amd64->IR: 0x48 0xCF 0xF 0x1F 0x0 0xFF 0xD2 0xCC 0x90 0x55
Should fix (Wine/Windows)
401719 (x86) sterrror_r on i686 causes a GPF
32-bit segreg problem; maybe we should fix?
n-i-bz (amd64) Support RDPMC ?
n-i-bz Improve PDB reading ? I thought I saw some patches for this ..
is it 253657 ? Who can help test this?
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
