D33259 hard-coded a linker flag relative to a linker library search path that should have allowed it to find libclang_rt.builtins-$ARCH.a under the resource directory automatically. Unfortunately, both the flag and the search path are incorrect, which leads to workarounds like double-suffixes in linker invocations.
The bare metal toolchain now uses a more standard hook to get the right arch-specific compiler-rt, and constructs a full path relative to the resource directory for the linker input.
Would it be possible to support the per-target runtimes directory layout as well?