Handle R_X86_64_DTPOFF64 #655
Merged
Conversation
This file contains 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
ultimaweapon
requested changes
Feb 18, 2024
mikusp
force-pushed
the
dtpoff64_relocation
branch
from
2e905c8
to
b3e979d
Compare
ultimaweapon
approved these changes
Feb 24, 2024
|
I merged main into this, so you should be able to merge this now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Created as draft, as I don't know what I'm doing there. DTPOFF64 seems similar to R_X86_64_64, but without including the base address. I'm not sure if that's a correct way or better to reuse Self::get_relocated?