[mimalloc] update to 2.1.7

[nickdademo]

• Changes comply with the maintainer guide.
• SHA512s are updated for each updated download.
• The "supports" clause reflects platforms that may be fixed by this new version.
• Any fixed CI baseline entries are removed from that file.
• Any patches that are no longer applied are deleted from the port's directory.
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Only one version is added to each modified port's versions file.

[nickdademo]

Not sure on the exact cause of the CI failures yet... If anyone has hints, please let me know :)

[dg0yt]

There is a test port, and you can install it locally with

vcpkg install --overlay-ports=scripts/test-ports vcpkg-ci-mimalloc

For x64-linux, the CI logs show:

undefined reference to `_mi_page_malloc_zero(mi_heap_s*, mi_page_s*, unsigned long, bool)'

The test port pulls source code from the mimalloc repo, so you must also update it now.

[dg0yt]

Still failing with

page.c:(.text+0x25fb): undefined reference to `_mi_page_malloc_zero(mi_heap_s*, mi_page_s*, unsigned long, bool)'

[nickdademo]

Still failing with

page.c:(.text+0x25fb): undefined reference to `_mi_page_malloc_zero(mi_heap_s*, mi_page_s*, unsigned long, bool)'

Are you able to post a link to this log? I didn't manage to find it :) Thanks!

[dg0yt]

You get to Azure pipeline by following the details links, then go to the assets, then find the download in the three dots on the right side when you hover the failure logs line.
#31357

It is a new mimalloc function, and I wonder if it is related to its extern inline definition. The command line doesn't set a C standard.

[Cheney-W]

Moving the PR to draft. Please set it to "ready for review" once the CI test passed.