https://bugs.kde.org/show_bug.cgi?id=444571

Carl Love <c...@us.ibm.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
             Status|REPORTED                    |CONFIRMED

--- Comment #10 from Carl Love <c...@us.ibm.com> ---
I found a Power 10 system with RHEL 9 installed.  Looks like there is a
compiler change that is now generating the lxsibzx and stxsibx instructions.  I
am seeing the instructions being generated on this system.

Fedora 34 has 
gcc (GCC) 11.2.1 20210728 (Red Hat 11.2.1-1)

dlclose_leak dump
....        x = memToLeak[-1];
    10000a90:   30 00 3f e9     ld      r9,48(r31)
    10000a94:   ff ff 29 89     lbz     r9,-1(r9)
    10000a98:   38 00 3f 99     stb     r9,56(r31)
    int i; for (i = 0; i < 2; ++i)


RHEL 9, gcc (GCC) 11.2.1 20210728 (Red Hat 11.2.1-2)

dlclose_leak dump
...
    x = memToLeak[-1];
    10000a94:   30 00 3f e9     ld      r9,48(r31)
    10000a98:   ff ff 29 39     addi    r9,r9,-1
    10000a9c:   1a 4e 00 7c     lxsibzx vs0,0,r9
    10000aa0:   38 00 3f 39     addi    r9,r31,56
    10000aa4:   1a 4f 00 7c     stxsibx vs0,0,r9
    int i; for (i = 0; i < 2; ++i)

The newer gcc is generating the instructions in question.

The test results are:
== 671 tests, 8 stderr failures, 1 stdout failure, 1 stderrB failure, 0
stdoutB\
 failures, 2 post failures ==
gdbserver_tests/hginfo                   (stderrB)
memcheck/tests/badrw                     (stderr)
memcheck/tests/bug340392                 (stderr)
memcheck/tests/linux/dlclose_leak-no-keep (stderr)
memcheck/tests/linux/dlclose_leak        (stderr)
memcheck/tests/linux/rfcomm              (stderr)
memcheck/tests/linux/sys-execveat        (stderr)
memcheck/tests/ppc64/power_ISA2_05       (stdout)
helgrind/tests/free_is_write             (stderr)
helgrind/tests/tls_threads               (stderr)
massif/tests/new-cpp                     (post)
massif/tests/overloaded-new              (post)

The test is failing.

I can now reproduce the bug.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to