Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upstage2: enable incremental MachO linking #6650
Merged
Conversation
kubkon
changed the title
|
cc @joachimschmidt557. After watching your brilliant talk on ARM backend at Zig Showtime, I thought this might interest you ;-) |
|
@kubkon Thanks! I'll have a look. I'm sure I'm going to learn something new. |
|
Nice work! |
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.
This PR enables basic incremental MachO linking. In other words, it is now possible to play with the biggest game changer of stage2 on a x86_64 mac like so:
Word of caution though that I haven't yet added handling of
__textsection growth meaning that if you apply too many growing changes, or add some rather beefy symbols, you will likely end up trapping at some point. I'm also not happy with handling of load command headers since we end up overwriting all at every change rather than only updating symbol and dynamic symbol tables for instance. This is to follow in a subsequent PR in the near future though ;-)