[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/arsenm/arm/runtime-libcalls-stop-excluding-generic-libgcc-functions'. Changed from 0000000000000000000000000000000000000000 to 9a85c264daab05b7226e58a0b9a564d519eed14e 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 9a85c264daab05b7226e58a0b9a564d519eed14e by Matt Arsenault on 21/07/2026 at 12:21.. ARM: Mark more generic libgcc functions as available Generic libgcc/compiler-rt functions coexist with aeabi variants (e.g., __divsi3 and __aeabi_idiv) according to my reading of the build. At least in compiler-rt, they are aliases (such that I'm not sure what the point of ever emitting the __aeabi name is). They were previously removed from the available set on AEABI+AAPCS targets to force selection of the preferred __aeabi_* variants, back when only one implementation per libcall could be recorded. Now that multiple implementations can be available per libcall, stop hiding the generics and select the __aeabi_* variant explicitly as the preferred implemntation. This reduces the number of special cases to consider for future libcalls info improvements. Co-authored-by: Claude (Claude-Opus-4.8) <[email protected]> https://invent.kde.org/qt/clang/llvm-project/-/commit/9a85c264daab05b7226e58a0b9a564d519eed14e