Skip to content

swift-reflection-dump: ELF ObjectMemoryReader support for relocations #27532

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 1 commit into from
Oct 4, 2019

Conversation

jckarter
Copy link
Contributor

@jckarter jckarter commented Oct 3, 2019

Collect the relative and symbol relocations from ELF images in order to resolve pointer values
read from disk. This allows us to enable symbolic-referencing-all-the-things for ELF platforms.

Collect the relative and symbol relocations from ELF images in order to resolve pointer values
read from disk. This allows us to enable symbolic-referencing-all-the-things for ELF platforms.
@jckarter
Copy link
Contributor Author

jckarter commented Oct 3, 2019

@swift-ci Please test

@jckarter
Copy link
Contributor Author

jckarter commented Oct 3, 2019

@davezarzycki Would you be able to test whether this works for you on your Fedora box? Instead of hardcoding specific relocation types I tried to use LLVM's queries as much as possible, so this is hopefully more resilient to non-x86 platforms or linker behavior variations.

@davezarzycki davezarzycki self-requested a review October 4, 2019 04:00
Copy link
Contributor

@davezarzycki davezarzycki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ninja check-swift-validation still passes on Fedora 31 (x86_64) with a unified build and top-of-tree llvm/clang/lld.

@jckarter jckarter merged commit a0f04ad into swiftlang:master Oct 4, 2019
@jckarter
Copy link
Contributor Author

jckarter commented Oct 4, 2019

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants