Revert "Add GP-relative relocations" #427
Merged
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.
This reverts commit d49e480.
Both the ePIC and FDPIC ABIs are expected to define relocation types which can be used for both PC-relative and GP-relative data, and are expected to define relaxations to optimize access to both types of data. Explicit, compiler-generated relocations using GP are only useful in cases where an object is known at compile time to be local and present in the GP-relative segment. The relaxations will result in GP-relative accesses, but the relocations involved will be linker internal and need not have allocated standard numbers.