The Windows malloc() implementation from MSVCRT is slow

Re:The Windows malloc() implementation from MSVCRT is slow by FreakLegion on Saturday July 02, 2022 @11:46PM (#31964873)

> Actually building a backwards-compatible binary that references old symbol versions is a gigantic pain: you either have to use a whole old environment, apply symbol versioning hacks on top of a new one and pray the resulting chimera works, or patch antique Glibc sources for new compilers and build a cross toolchain.

This is the example I gave downthread. It's an everyday problem for a lot of developers targeting Linux, whereas targeting decades-old Windows versions is a breeze.

Glibc isn't better, it just has different problems.

[ Parent | on HN ]

Re:The Windows malloc() implementation from MSVCRT is slow by seba_dos1 on Sunday July 03, 2022 @01:40PM (#31969450)

Targeting old GNU/Linux is a breeze too. Containers make compiling stuff for old distros super easy. I even use them to crosscompile stuff for Windows, macOS, Android etc. too, since I got tired of having to set up development environments on new machines.

[ Parent | on HN ]