[Bug objc/126839] [17 Regression] Many objc failures since r17-2156-g6317befec9

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=126839

--- Comment #1 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Hans-Peter Nilsson from comment #0)
> Ever since r17-2156-g6317befec9, "most" objc execution tests fail for
> cris-elf and pru-elf, perhaps for others.  I don't know wat the common
> factor is; it could be 32-bit, bare-iron (*-elf) targets or cross builds. 
> To me, the commit has no obvious clue what could be amiss.

Sorry for the breakage - but likewise it is not obvious to me (GNU runtime
builds and runs on both ELF and Mach-O hosted systems).

Please could you post the configuration info and the version of binutils needed
to repeat this).  I don't think that there's anything in the metadata
generation that should depend on hosted/bare metal -- but there could be things
that depend on the linker in use .. Presumably, libobjc is linked statically;
that could be completely untested on hosted systems.

> Before dying, there's a message in objc.log, for example:
> spawn pru-elf-run ./bitfield-1.exe^M
> objc runtime: cannot find class Object^M

That is the clue, I suppose, but I'll likely need to side-by-side the metadata
to figure out what has changed (nothing was supposed to have changed - this was
'just' making sure the meta data constructors had properly typed elements).