Use VirtualAlloc() on WIN32

[aitap]

Hello again,

Here's the pull request I've been meaning to submit back in 2020. This makes use of VirtualAlloc on WIN32 to allocate memory dynamically instead of relying on INTERNAL_MEMORY_SPACE. After ./configure --host=x86_64-w64-mingw32 I can rename and manually run the dmalloc_fc_t and dmalloc_t executables with the arguments specified for the light and heavy Makefile targets; the tests pass.

[j256]

Thanks for this! I'm pretty ignorant of the Windows side of the fence. Does it make more sense to check for the include file and check for existance of the VirtualAlloc() method as opposed to just testing for WIN32?

[aitap]

I can't say no with 100% confidence.

People have been discussing configure tests for WinAPI in the past, but most projects seem to rely on preprocessor symbols pre-defined by the compiler (e.g. SQLite tests for _WIN32_WINNT). _WIN32 is among the Microsoft-predefined macros that everyone tests for.

On the other hand, the ancient documentation says this function is to be found in windows.h, while the current documentation (Windows ≥ XP, 2003) says "include windows.h, memoryapi.h". (And the current code in the pull request only includes memoryapi.h.)

Judging by old StackOverflow questions, older Windows SDKs may indeed lack memoryapi.h. Currently, windows.h includes memoryapi.h through winbase.h, but that doesn't seem to be documented.

I'll search the documentation some more and implement a configure test choosing between windows.h / windows.h+memoryapi.h if I don't find anything more definitive.

[j256]

Thanks. I appreciate the work. Yeah I'd rather test for existence of the function and the includes as opposed to a compiler symbol.

[aitap]

Here are the configure tests. I made heap.c include conf.h. Would you like me to figure out a way to give it the flags via the compiler command line? Any other fixes it needs?