[qt/clang/llvm-project]: Summary of bulk changes made

KDE Git Services - Bulk Change <[email protected]>
Newsgroups gmane.comp.kde.cvs
Message-ID <[email protected]>
Git repository change summary for qt/clang/llvm-project
Pushed by mirror-service into branch 'upstream/users/jrtc27/lld-test-ppc32-ifunc-nonpreemptible'.
Changed from 0000000000000000000000000000000000000000 to 4e1dfc1c8ecaccf0e7de350277385296a91e35b3
Acknowledgement was received that this change introduces only existing code that has been pushed to another public open source repository.

This change contains the following new commits:

Git commit a9530be6df0743d13bab49f9eca022ee827668f5 by Jessica Clarke on 19/07/2026 at 16:16..
[NFC][test][ELF] Check DSO's ifunc2 is in .iplt in aarch64-ifunc-bti.s

This mirror's the PIE's CHECK lines, which were already stricter.
https://invent.kde.org/qt/clang/llvm-project/-/commit/a9530be6df0743d13bab49f9eca022ee827668f5

Git commit 4e1dfc1c8ecaccf0e7de350277385296a91e35b3 by Jessica Clarke on 19/07/2026 at 16:16..
[NFC][test][ELF] Improve ppc32-ifunc-nonpreemptible-(no)pic.s

Firstly, the nopic test had an unused HEX check line when it should have
been checking .got.plt, and the pic test was only checking .got2, also
ignoring .got.plt.

Secondly, the indentation for instructions was inconsistent within a
single file.

Thirdly, neither test was actually checking the code for func's IPLT
entry in .glink, only that the symbol existed as a normal function that
wasn't the same as the resolver, and the nopic test wasn't even testing
the full contents of the PLT call stub, which was inconsistent with the
pic test.

Fourthly, the pic test used the same output file for two different
links, which can be confusing when debugging.

Finally, the comment at the start of the pic test's PLT call stub had no
bearing on the immediate in use, instead being the same as the nopic's
one with the 4 subtracted from both sides (presumably trying to account
for the nopic test not having the extra .got2 entry, but neglecting the
fact that it's not using absolute addressing, and even if it were, the
addresses are entirely different).
https://invent.kde.org/qt/clang/llvm-project/-/commit/4e1dfc1c8ecaccf0e7de350277385296a91e35b3
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.