Right now they fail with messages like this:

[46/50570] LINK(DLL) test_shared_library.dll test_shared_library.dll.lib test_shared_library.dll.pdb
FAILED: ...
error: SECREL relocation points to a non-regular symbol: __ImageBase
[47/50570] LINK(DLL) base_profiler_test_support_library.dll base_profiler_test_support_library.dll.lib base_profiler_test_support_library.dll.pdb
FAILED: ...
error: SECREL relocation points to a non-regular symbol: __ImageBase
[48/50570] STAMP obj/chrome/browser/ui/webui/omnibox/mojo_bindings_blink__type_mappings.inputdeps.stamp

[40/58599] LINK(DLL) test_shared_library.dll test_shared_library.dll.lib test_shared_library.dll.pdb
FAILED: ...
error: SECREL relocation points to a non-regular symbol: ___safe_se_handler_table

LLD started relocating .debug$S sections in r305713, which was four days ago.

The basic issue is that .debug$S sections contain lots of SECREL and SECTION relocations. Until recently, those relocations only worked on "regular" symbols. Because the CRT's debug info is vast and wide, we are now seeing these relocations applied to absolute symbols, common symbols, garbage collected symbols, synthetic linker provided symbols, etc. We need to handle these relocations against all these different symbol types in LLD.