Conversation
The goal is to be able to reuse a single `.ji` for multiple code caches.
Member
|
Can we make the split files valid SO's with DT_NEEDED links? Not sure I like the idea of needing a specific side file with a separate lookup mechanism. |
Member
Author
I don't think so. The idea is:
Instead of what we have currently:
The reason for the split was that otherwise we would need to use an elf/coff/mach-o parser just to figure out if the cache file is valid, since dlclose doesn't work properly... |
Member
|
We control the layout of the shared objects - e.g. we can make the ji part a separate load command. We don't need a full parser, these data structures should be traversable in like 30-40 lines of code. |
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
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.
The goal is to be able to reuse a single
.jifor multiplecode caches. Still work-in-progress currently this doesn't
produces usable code caches.
With this:
Making it clear that the biggest cost remains the data.