News for hackers. Stuff that matters.

A comment on The Windows malloc() implementation from MSVCRT is slow. Parent comment

Re:The Windows malloc() implementation from MSVCRT is slow by TonyTrapp on Saturday July 02, 2022 @05:40PM (#31962719)
> It was in the past. At first msvcrt.dll was the runtime library used up to Visual C++ 6.

At that time it was already a big mess, because at first it was the runtime library of Visual C++ 4 in fact! The gory details are here: https://devblogs.microsoft.com/oldnewthing/20140411-00/?p=12...

> some system components still link to it

Some system components themselves are very much ancient and unmaintained and only exist for backwards compatibility as well.

[ Parent | on HN ]
Re:The Windows malloc() implementation from MSVCRT is slow by garaetjjte on Saturday July 02, 2022 @06:37PM (#31963105)
Ancient or not, I don't think it really matters for allocation performance: malloc in both msvcrt.dll and ucrtbase.dll after some indirection ends up calling RtlAllocateHeap in ntdll.dll
[ Parent | on HN ]
Re:The Windows malloc() implementation from MSVCRT is slow by TonyTrapp on Sunday July 03, 2022 @06:31AM (#31966620)
It does, because modern allocators do a lot of house keeping on top of the system heaps, e.g. to quickly reuse identically-sized memory chunks that were just freed.
[ Parent | on HN ]
Re:The Windows malloc() implementation from MSVCRT is slow by jasomill on Sunday July 03, 2022 @02:04AM (#31965468)
For posterity, here's a link to a version of that page with the original comments section intact:

https://web.archive.org/web/20160410051513/https://blogs.msd...

[ Parent | on HN ]