https://bugs.kde.org/show_bug.cgi?id=418435
--- Comment #1 from Andreas Arnez <ar...@linux.ibm.com> --- The issue seems to be caused by the handling of the s390x instruction CLC, see s390_irgen_CLC_EX(). When comparing two bytes from the two input strings, the implementation uses the comparison result for a conditional branch to the next instruction. But if no further bytes need to be compared, the comparison result is also used for generating the resulting condition code. There are two cases: 1. The inputs are equal. Then the resulting condition code is zero. This is what happens in the memcmp test case. 2. The inputs are different. Then the resulting condition code is 1 or 2 if the first or second operand is greater, respectively. At least in the first case it is easy to avoid the additional dependency, by clearing the condition code explicitly. -- You are receiving this mail because: You are watching all bug changes.
