←back to thread

383 points hkalbasi | 1 comments | | HN request time: 0.211s | source
Show context
devit ◴[] No.42814926[source]
I think the optimal approach for development would be to not produce a traditional linked executable at all, but instead just place the object files in memory, and then produce a loader executable that hooks page faults in those memory areas and on-demand mmaps the relevant object elsewhere, applies relocations to it, and then moves it in place with mremap.

Symbols would be resolved based on an index where only updated object files are reindexed. It could also eagerly relocate in the background, in order depending on previous usage data.

This would basically make a copyless lazy incremental linker.

replies(9): >>42815042 #>>42815180 #>>42815279 #>>42815434 #>>42815474 #>>42815621 #>>42815660 #>>42815894 #>>42815895 #
1. ignoramous ◴[] No.42815474[source]
> Symbols would be resolved based on an index where only updated object files are reindexed. It could also eagerly relocate in the background, in order depending on previous usage data.

Not exactly this, but Google's Propeller fixes up ("relinks") Basic Blocks (hot code as traced from PGO) in native code at runtime (like an optimizing JIT compiler would): https://research.google/pubs/propeller-a-profile-guided-reli...