-
Notifications
You must be signed in to change notification settings - Fork 41
Improve automatic symbol pairing for nameless literals #247
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 6 commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
88cc76d
Improve automatic symbol pairing for nameless literals
LagoLunatic f8e7478
Fix data reloc diffing when the reloc points to an in-function static…
LagoLunatic 40f7791
Only pair up literals that match perfectly
LagoLunatic 81163a6
Clippy
LagoLunatic 8e4615e
Do two separate passes when pairing up literals
LagoLunatic 5b8009e
Fix partially-matching literal pairups not working right
LagoLunatic 8807580
Remove duplicate $ splitting code
LagoLunatic 3e74225
Implement $ splitting for section names too
LagoLunatic f50569e
Merge branch 'main' into literal-matchup
encounter b72355d
Merge branch 'main' into literal-matchup
encounter c6437b4
Minor cleanup
encounter File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Curious if we'd want other logic for GCC or MSVC
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking at the
vs2022.o
object in the tests, I see some literals like__real@3f800000
, so I guess MSVC already puts the value of float literals in their symbol name. So ones like these shouldn't need any special logic, as comparing literals by value is what would be done anyway if name was ignored.Other than float literals I'm not really sure what I'm looking at, but I see some things like:
$unwind$?Dot@Vector@@QEAAMPEAU1@@Z
_RTC_InitBase.rtc$IMZ
$pdata$?DistSq@Vector@@QEAAMPEAU1@@Z
I imagine some of these might need their own logic to pair them up properly, but it's hard to tell with just one object, someone would need both the target and the base to guess what's going on here.