WTF::String is used in QHash (as WTF::HashMap), but didn't have a
qHash() function itself. Instead, the 1-to-2-arg adapter was used,
which ended up calling the QString overload (QString is a public base
class of WTF::String).

With a deprecated or =delete'ed adapter, this causes a warning/error.

Fix by providing a hidden friend qHash() for WTF::String. It can just
delegate to the QString one, too, and, since this is private API, we
don't need to emulate the adapters seed handling, which differs from
just passing the seed to the QString qHash().

For what it's worth, this also restores consistency of hash value
between equal QString and WTF::Strings.

Amends 94f5a6ec6d81f262be6fc3de1c11f2742bb05196 (5.2).

Pick-to: 6.11 6.8
Task-number: QTBUG-145828
Change-Id: I8fe0ef8db0bcbf0434d33bc0acd80bd541fe4354
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>

Qt 5.15 for VxWorks had JIT and this change brings back this feature.

Task-number: QTBUG-133449
Pick-to: 6.8 6.10
Change-Id: I0ce487ca01e5578f47fdb5cddac9ea4e5804b857
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>

case conversions are now separate from other properties.

See commit 763f19151cc31ca1ba4912e0828359be5dba89e8 in qtbase.

Pick-to: 6.10 6.8 6.5
Change-Id: Ia13f515e613c7470f816c9930e870e391c88e367
Reviewed-by: Marc Mutz <marc.mutz@qt.io>

The function name had a spelling error. This change improves code
readability and follows Qt naming conventions.

Change-Id: Ic0646ea679bf3619691b6a581ba5ef589e7827bd
Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>

V4's baseline JIT uses some old JavaScriptCore code to
optimize functions.

As part of the offering, it is possible to use a disassembler, if
enabled, to peek into the code that the JIT has generated for a
function.

For i386 and x86_64 udis86 is used, of which we bundle a very old
version.

To build and make use of udis86 it is necessary to generate some code
running some bundled python scripts.

The scripts are still written for a python2 target, which has long been
sunsetted, making the scripts difficult to run on more modern systems.

To allow the scripts to be run more easily, some modifications were made
to support more modern pythons versions.

In particular, print statements were modified to print functions.

Furthermore, usages of the division operator("/") were modified to the
integer division operator("//"), as the meaning of "/" was changed to
non-integer division between python 2 and 3.

Finally, a usage of the sort method was modified with self assignment to
a `sorted()` value, due to python 3 not returning a list anymore, which
has a sort method, on dict's `items` method.

The changes are expected to mostly be semantically compatible, albeit it
wasn't ascertained whether the behavior of other parts of the script
might have been silently hit when running on a more modern python
version.

Informally, the script was used with a python 3.13 version, and the
generated code was used to disassemble a few jitted function with
success during an unrelated bug investigation.

Change-Id: Ide0bcf4d29a51759f9bb9bd07d940562a8cfcc04
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>

[ChangeLog][Third-Party Code] Added PURL and CPE information to the
attribution files of 3rd party sources.

Pick-to: 6.5 6.8 6.9 6.10
Fixes: QTBUG-137262
Task-number: QTBUG-129602
Change-Id: I1a5691ff042c47461fe4769399c3bd2d6ec52160
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>

Change the compiler/platform detection macros to check whether a macro
is defined, before testing its value. See also the discussion at

https://bugs.webkit.org/show_bug.cgi?id=167643
https://codereview.qt-project.org/c/qt/qtbase/+/618094

Task-number: QTBUG-132900
Change-Id: Ic3cc02b23e034cc7622e899b4acc381166a9ec95
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>

When VxWorks is configured with RTP_MEM_FILL false for performance
reasons, then it is not filling the allocated memory to 0, causing
the QML engine to crash, because it is expecting that it is filled
with 0s. This change handles this scenario by calling memset 0 on
the allocated memory. Qt needs to be configured with
QT_RTP_MEM_FILL define.

Task-number: QTBUG-133305
Pick-to: 6.8 6.9
Change-Id: I885c3cad7d81a11b8a0c125ddc098751b9643392
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>

... and make it actually compile.

... and set the flag for JIT pages being prepared. We are clever enough
not to make them executable right away.

Pick-to: 6.9 6.8
Task-number: QTBUG-131957
Change-Id: I07dc6a9c8ec7d0881d73fc5bd44a6059f66dd2eb
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>

Since we cannot figure out what exactly has to be done to prevent the
JIT from crashing, we perform a partial revert of commit
912af1e8b4c1f62802a3e0a4b428bb4e9f4d2c90, only for this platform.

The bug fixed by the original change is specific to linux. Therefore
this doesn't cause any real harm.

Pick-to: 6.9 6.8
Fixes: QTBUG-131957
Change-Id: Ic3baf32aae1f0f2feb9abc34b9f43a5db867165b
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>