Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54581

Signed-off-by: Torge Matthies <tmatthies@codeweavers.com>

Signed-off-by: Torge Matthies <tmatthies@codeweavers.com>

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54557

Signed-off-by: Marcus Meissner <marcus@jet.franken.de>

Introduced by commit a97fd9f2

Signed-off-by: Tingzhong Luo <luotingzhong@uniontech.com>

We don't have to reset pos and the sortkey state for every iteration of
the for-loop. In most cases the previous iteration's values are still
valid, and can be re-used, skipping a lot of duplicate work.
Signed-off-by: Torge Matthies <tmatthies@codeweavers.com>

If I'm interpreting this code correctly, once either of these two
if-conditions are true once, they will also be true at some point
during all of the remaining iterations of the for-loop. Thus, we can
just stop the for-loop here.
Signed-off-by: Torge Matthies <tmatthies@codeweavers.com>

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=53176

Even though this is a waste of memory it seems to trip on some UAF with
some games.

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54475

Chr() depends on the thread's ANSI code page which in some cases is different
from the Windows ANSI code page (e.g. hi-IN).

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54003