Found the same problem reported with mono (.NET), seems an LLVM bug or LLVM compatibility issue.

cc @lhames

@swift-ci create

This is a relocation-out-of-range assertion. It's triggered when the RuntimeDyld::MemoryManager instance allocates two sections out-of-range of one another. I wouldn't have expected this to happen on Linux if we're using the large code model, but I don't know the ELF/AArch64 combination well, so it's possible that this is expected behavior.

We could work around this by pre-allocating a slab of memory in the memory-manager, but I think the right long term solution is to move to JITLink. A backend has been started by Stefan Granitz in https://reviews.llvm.org/D108986, and can probably be completed before LLVM 14 is released. I have filed https://llvm.org/PR51924 to track this.