On 17/07/2020 12:29, Andrew Stubbs wrote:
For easier later maintenance, shouldn't this be a '#define' (or similar)
done next to where the GCC back end defines its default?
I thought of this, but I don't think there's actually a problem. The
default is defined via OPTION_DEFAULT_SPECS, so there ought to be an
explicit option passed to mkoffload at all times. If that's not the case
I think the problem lies elsewhere.
Oh, I forgot, that would be true if mkoffload were called by the offload
compiler, but it's called by the host compiler, so the specs won't help.
If we want mkoffload to respect --with-arch then the value will have to
be acquired some other way.
I suspect that --with-arch only works properly in conjunction with
--disable-multilib, so maybe this is just part of a bigger issue (which
I don't intend to spend time on now).
Andrew
