https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114718
Bug ID: 114718
Summary: GCN's '-march'es vs. default multilib
Product: gcc
Version: 14.0
URL: https://github.com/gcc-mirror/gcc/commit/1bf18629c54ad
f4893c8db5227a36e1952ee69a3#commitcomment-140648051
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: tschwinge at gcc dot gnu.org
CC: ams at gcc dot gnu.org
Target Milestone: ---
Target: GCN
When a specific multilib build for GCN's '-march'es is not available (has not
been 'configure'd/packaged), GCC resorts to the default multilib build -- which
in the case of GCN won't even link: 'ld: error: incompatible mach'. Instead of
attempting the latter (default multilib build), should this case be diagnosed
properly, instead?
(Independent of the vague idea that multilib builds for GCN be made "more
permeable".)
Reported, for example, by Oscar Barenys in
<https://github.com/gcc-mirror/gcc/commit/1bf18629c54adf4893c8db5227a36e1952ee69a3#commitcomment-140648051>.
