Remove the need for `loader_link_address`

[Ivan-Velickovic]

We should look into removing the loader_link_address as it is fragile and also platform-specific.

The main issue that I've encountered is that we usually place loader_link_address somewhere near the start of main memory, the loader code itself goes at loader_link_address and then directly after is the binary data for the kernel and the initial task. These are then relocated to specific places in memory decided by the tool. What happens when you have really large images is that the regions that have to be copied around end up overlapping with the location of the loader itself.

I've had to do work-arounds like #206 and #476.

[Indanz]

Why not make the loader position independent and then just place/move it anywhere?

[Ivan-Velickovic]

Why not make the loader position independent and then just place/move it anywhere?

Yes that's the plan, forgot to mention in the issue. There's a bit more work in addition to make the loader smarter so that it can relocate itself such that it doesn't try to later copy over itself.