https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111065
--- Comment #4 from Kito Cheng <kito at gcc dot gnu.org> --- I guess I skip too much detail here, the multilib for linux isn’t really honor to the reause rule in the multilib config file for a while. That just control how multilib build, e.g. build ilp32 with which arch, and we will find matched ABI, but why we did that? The reason is simplify the reuse rule, RISC-V has huge number of extension now, so enumeration the possible combination are almost impossible. But why it can’t use same scheme as baremetal? Okay, that’s because we encode the abi in the path only, unlike baremetal we have encode both abi and arch, it kinda of de facto ABI in linux/glibc, also it not make too much sense to having too much different multilib within a (RISC-V) linux system.
