Prevent link failure when there are multiple alias definitions pointing to the same symbol#1021
Merged
Merged
Conversation
…ng to the same symbol
c7a7bb6 to
0af0b06
Compare
davidlattimore
approved these changes
Aug 3, 2025
AadiWaghray
pushed a commit
to AadiWaghray/wild
that referenced
this pull request
Aug 10, 2025
…ng to the same symbol (wild-linker#1021)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
In the current implementation, if copy relocations exist for non-weak symbols with the same address, wild will bail with the error. However, since this would incorrectly treat multiple alias definitions pointing to the same symbol as invalid code (see copyrel.sh), it would be better to simply issue a warning instead.