To be fair, the documentation (as of today) doesn't say anything about GNU ld being broken/unusable, only slower than lld. It should maybe be worded differently if using GNU ld is wrong.
GNU ld wasn't broken until 2 days ago, and it may not be permanently broken (we need OG back in France to find out though).
I'm of the opinion that this is a major enough issue affecting enough people who use the 100% mamedev.org approved/published tool package in Windows that code reverting or placing in a branch would be a great option until such time work can be done to address the issue. The response has been, in my opinion, lackadaisical. It didn't affect the more prominent developers, so there has been little effort put in to make it better for those who are struggling to find a solution. For my circumstances, LLD is not an option due to issues related to using RAMDISK as the storage for compiling (saving on hardware thrashing) and not being handled properly by the linker. I will be exploring this further to see if either a cutting edge LLD or something prior to the version issued around the time the compile package was assembled.
Anyway, until things square away, my testing efforts will be at a minimum or not nearly at all as my local machine struggles to compile, especially since CPU-base Video is my only choice meaning that I can do literally nothing else while compiling for 1-2 hours. If OG will be gone for more than a couple days, please consider stowing the changes away for now. The last couple days have been pretty discouraging.