https://bugs.kde.org/show_bug.cgi?id=295974
--- Comment #12 from Mark Wielaard <[email protected]> --- (In reply to mcermak from comment #10) > Hello Sasshka, > > the attached patch makes sense to me. Comparing patched and unpatched > sources, I see in both cases: > > $ tests/vg_regtest none/tests/amd64/sse4-64.vgtest > none/tests/x86/sse4-x86.vgtest > sse4-64: valgrind -q ./sse4-64 > sse4-x86: valgrind -q ./sse4-x86 > > == 2 tests, 0 stderr failures, 0 stdout failures, 0 stderrB failures, 0 > stdoutB failures, 0 post failures == > > Which is expected. Looking closer, the patched binary shows the expected > logs (while the unpatched doesn't): > > $ ../../../vg-in-place ./sse4-x86 |& fgrep pextrd > r pextrd $0 60b160857d45c48447b8d8c0eeef1e50 5555555555555555 > 00000000eeef1e50 > m pextrd $0 60b160857d45c48447b8d8c0eeef1e50 5555555555555555 > 55555555eeef1e50 > r pextrd $1 60b160857d45c48447b8d8c0eeef1e50 5555555555555555 > 0000000047b8d8c0 > m pextrd $1 60b160857d45c48447b8d8c0eeef1e50 5555555555555555 > 5555555547b8d8c0 > r pextrd $2 60b160857d45c48447b8d8c0eeef1e50 5555555555555555 > 000000007d45c484 > m pextrd $2 60b160857d45c48447b8d8c0eeef1e50 5555555555555555 > 555555557d45c484 > r pextrd $3 60b160857d45c48447b8d8c0eeef1e50 5555555555555555 > 0000000060b16085 > m pextrd $3 60b160857d45c48447b8d8c0eeef1e50 5555555555555555 > 5555555560b16085 > $ > > Nice. No regression spotted. So there is a lot of change in the .exp file because the new test is added in the middle: // ------ SSE 4.1 ------ test_PINSRD(); + test_PEXTRD(); test_PMAXSB(); test_PMAXSD(); test_PMAXUD(); Please add it to the end, so you only have to add a few new lines to the .exp file. -- You are receiving this mail because: You are watching all bug changes.
