[qt/qt/qtbase]: Summary of bulk changes made

Git repository change summary for qt/qt/qtbase
Pushed by mirror-service into branch 'dev'.
Changed from 2ef60b71530ce8fc330d54a2d79c02e4cd661138 to 5b048f9c4633d709442176e10c1c8e0cb384ae98
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 53a7815c790550b0d249486008ce86563a79ab96 by Christian Ehrlicher on 03/08/2026 at 19:55..
QRhiD3D12: make static const members constexpr to avoid linker error

The static const members need to be constexpr when compiling with
llvm-mingw - otherwise there will be an undefined reference, at least
when doing a unity build.

Pick-to: 6.12 6.11
Change-Id: Iacd3bf17c4ef364bbc43c51229fd832f2dc96e33
Reviewed-by: Laszlo Agocs <[email protected]>
https://invent.kde.org/qt/qt/qtbase/-/commit/53a7815c790550b0d249486008ce86563a79ab96

Git commit fc75e0a87205526e198d79898fff69f6aa65a2d5 by Mylo Fawcett on 03/08/2026 at 19:55..
qpa/wayland: Only enable text-input-v3 surfaces when needed

Since a2bc24c05189f9d39c034560f163ad1490c37996,
enabling and disabling surfaces in text-input-v3 has been tied to
receiving enter and leave events for those surfaces. This is incorrect
as a surface may be entered but should not be enabled, for example if
the current focused object does not support text input.

[ChangeLog][QtCore][qpa/wayland] Make it so that surfaces under
text-input-v3 are only enabled if they are entered and want to receive
text input.

Fixes: QTBUG-146211
Pick-to: 6.12 6.11
Change-Id: I50cefdae8b99c074bc628a6b1042633519a8f2f2
Reviewed-by: David Edmundson <[email protected]>
https://invent.kde.org/qt/qt/qtbase/-/commit/fc75e0a87205526e198d79898fff69f6aa65a2d5

Git commit 4e7b660edcb3e23b41efa1351f03f6b6791612c9 by Jean-Michaël Celerier on 03/08/2026 at 19:55..
stylesheet: fix build on windows when no style-windows feature

Pick-to: 6.12 6.11
Change-Id: I29f0bd2642c7b0db60a69809e1244aa6406ea752
Reviewed-by: Christian Ehrlicher <[email protected]>
https://invent.kde.org/qt/qt/qtbase/-/commit/4e7b660edcb3e23b41efa1351f03f6b6791612c9

Git commit 5b048f9c4633d709442176e10c1c8e0cb384ae98 by Marc Mutz on 03/08/2026 at 23:33..
QRhiVulkan: shrink frame size of printDeviceLossErrorInfo()

The function's frame size was reported to be > 70KiB, far exceeding
our goal (not yet enforced) of 20KiB.

This is primarily due to the use of a QVLA<VkDeviceFaultVendorInfoEXT>
where the struct has a char description[256], so that field alone
counts for 64KiB of stack frame size (when multiplied with the default
QVLA Prealloc of 256).

This function is not performance-critical, seeing as it's called only
after qWarning()s, so is on the cold path, anyway, but even if it
were, QVLA value-initializes the elements on resize(), yet
vkGetDeviceFaultInfoEXT() will overwrite everything, anyway, so QVLA
is zeroing out all that memory for nothing.

Use q20::make_unique_for_overwrite() instead. While that goes to the
heap, unconditionally, incl. for zero-size, it critically doesn't
value-initialize the array, regaining some of the overhead caused by
heap use.

Also mark the whole function as cold, so optimize-for-size covers the
whole function and not just the code after the first qWarning(),
probably avoiding a .clone.cold/hot split of the function.

My Vulkan isn't new enough to support these APIs, so I cannot check
how much text size this saves.

Amends 6da0a51f1a04bc0cce787b61614ddb3dad3c38d2 (6.12).

Pick-to: 6.12
Change-Id: Ic01b89713a727280fc3e745c9eb0ffc1dcd50466
Reviewed-by: Aurélien Brooke <[email protected]>
Reviewed-by: Laszlo Agocs <[email protected]>
https://invent.kde.org/qt/qt/qtbase/-/commit/5b048f9c4633d709442176e10c1c8e0cb384ae98