[Swift+WASM] [IRGen] Disable COMDAT for reflection metadata #24133
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
LLVM's Wasm COMDAT code assumes each COMDAT will be in its own section. This works for C++ on Clang, since each COMDAT is emitted into its own .rodata. section, but not for Swift metadata, which are all placed in the same section.
Disable COMDAT support when emitting reflection metadata.
This matches the behaviour on ELF (where COMDATs are disabled) and MachO (which doesn't support COMDAT)
This shouldn't affect existing platforms.
@ddunbar @MaxDesiatov This avoids an LLVM assert when building stdlib for WebAssembly: should be helpful for SR-9307.
@compnerd: You added the COMDAT support originally for Windows/COFF, right? Should the check for COMDAT support use a whitelist instead of a blacklist, since ELF, MachO, and now WASM all disabled it?