https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96973
Iain Sandoe <iains at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |iains at gcc dot gnu.org
--- Comment #5 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Francois-Xavier Coudert from comment #3)
> In macho_add_fat(), the code correctly identifies 2 archs, with the right
> types (first i386, then x86_64). It's then calling macho_add() for the
> x86_64 arch, with an foffset of 0x0000b00000000000, which looks very weird
> to me.
>
> That code has a FIXME, so maybe that's the issue?
>
> /* FIXME: What about cpusubtype? */
cpu subtype is about x86_64/x86_64h or ppc601 c.f ppc7400 slices - it should
not be relevant in cases we'll encounter at present in GCC. I suppose that it
could conceivably be tricky if we have two slices that are valid for the
current arch (we'd have to figure which one was going to be selected).
It might be some future GCC version could have slices for x86_64, x86_64h and
arm64 / arm64e - we would then need to revisit this.
