roc-lang/roc
1
1
Fork 0
mirror of https://github.com/roc-lang/roc.git synced 2024-09-21 15:59:20 +03:00
Code Issues Packages Projects Releases Wiki Activity
3baff93a97
roc/linker
History
Brendan Hansknecht a593713800 Fix surgical linking for C hosts with extra arg
2021-09-23 21:29:53 -07:00
..
src Move copying precompiled host to rebuild thread 2021-09-18 17:54:02 -07:00
tests/fib Merge branch 'trunk' into integrate-linker 2021-09-21 09:39:47 -07:00
Cargo.toml Add surgical linking to frontend with simple dummy lib creation 2021-09-14 23:06:22 -07:00
README.md Fix surgical linking for C hosts with extra arg 2021-09-23 21:29:53 -07:00

README.md

The Roc Surgical Linker

This linker has the goal of being extremely slim lined and fast. It is focused on the scope of only linking platforms to Roc applications. This restriction enables ignoring most of linking.

General Overview

This linker is run in 2 phases: preprocessing and surigical linking.

Platform Preprocessor

  1. Dynamically link the platform to a dummy Roc application dynamic library
  2. Create metadata related to Roc dynamically linked functions
    • Symbols that need to be redefined
    • Call locations that need to be modified for each symbol
    • Locations of special roc functions (roc_alloc, roc_dealloc, builtins, etc)
  3. Modify the main executable to no longer be dynamically link
    • Delete dependency on dynamic library
    • Remove symbols from the dynamic table (maybe add them to the regular table?)
    • Delete GOT and PLT entries
    • Remove relocations from the dynamic table
    • Add extra header information about new text and data section at end of file

Surgical Linker

  1. Build off of preprocessed platform
  2. Append text and data of application, dealing with app relocations
  3. Surgically update all call locations in the platform
  4. Surgically update call information in the application (also dealing with other relocations for builtins)

TODO (In a lightly prioritized order)

  • Run CLI tests and/or benchmarks with the Roc Linker.
  • Test with an executable completely generated by Cargo (It will hopefully work out of the box like zig).
  • Add Macho support
    • Honestly should be almost exactly the same code. This means we likely need to do a lot of refactoring to minimize the duplicate code. The fun of almost but not quite the same.
  • Add PE support
    • As a prereq, we need roc building on Windows (I'm not sure it does currently).
    • Definitely a solid bit different than elf, but hopefully after refactoring for Macho, won't be that crazy to add.
  • Look at enabling completely in memory linking that could be used with roc run and/or roc repl
  • Add a feature to the compiler to make this linker optional.