Pretty much every other GPU targeted language either does a runtime compilation from source or IR.
This has been a known problem+solution for ages and their approach to ROCm is flummoxing.
With ROCm on 5000 series they promised status updates several times which never came and the eventual unofficial support came after 6000 series was out. Then with the Rx580 support, they claimed that while it was unsupported it should still work and several of their developers claimed to be looking into the matter. I recall other similar incidents regarding their other smaller projects under GPUOpen. So overall it always seemed like they weren't really communicating properly internally, thus leading to all of their projects seeming somewhat disconnected from each other.
So not only does it mean that you have to choose which hardware you want to support at any point in time but you have to maintain your codebase and release new binaries every time AMD releases a new GPU.
And it gets even more complicated because even intra-generation compatibility isn’t granted since differ GPUs from the same generation can have slight variances in them that essentially requires you to target them specifically.
On the other hand CUDA binaries that date back to the days of Tesla and Fermi can still run on current hardware with no issues.
The architecture behind ROCm does not make any sense outside of custom implementations for supercomputers and bespoke hyperscaler size deployments.
That's also why they struggle to support new consumer hardware, why they led people on about ROCm on 5000 series until 6000 series was around the corner (this move killed my interest in taking ROCm seriously for the near future) and why they dropped support for the rx580 when it was the only consumer GPU that was still available with ROCm.
They're going to have to fundamentally redesign ROCm's build process to come anywhere near CUDA's level of support.