Re: nds broken by recent patches

On 28 Jan 2022 14:54, Jeff Law wrote:
> On 1/28/2022 9:36 AM, Jeff Law wrote:
> > For example, someone mucked up the compiler for or1k-elf at the same 
> > time you're doing your refactoring.  Now I've got a patch to fix the 
> > compiler ICE, *but* I'm also getting a crap-ton of new testsuite 
> > failures in the testsuite due to missing _init/_fini symbols.  I don't 
> > know yet if that's a newlib issue or something else mucked up on the 
> > compiler side.
> 
> I think I've tracked this done.  The change to internalize 
> HAVE_INITFINI_ARRAY wasn't complete.  It missed newlib.  Affects 
> aarch64, arm, or1k and cris -elf ports.  I don't test for former pair, 
> but I do test the latter pair.   or1k and cris fail differently. 
> or1k-elf code fails to link, while cris-elf fails a few tests that rely 
> on ctor/dtor support.

thanks ... the expectation was that things outside of newlib weren't
relying on this, but i think it's prob OK for libgloss to.  not great,
but not entirely unreasonable.  not sure what you meant by "it missed
newlib" as your fix only touches libgloss.  assuming that was a thinko.
-mike

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEuQK1JxMl+JKsJRrUQWM7n+g39YEFAmH0zWMACgkQQWM7n+g3
9YHd0RAAyIupM0SWBzPWJMAYqH2vbDmd7lI85aHIEeWzDGOshGzSzbjcB9VogWbO
5jxVQt1z5Wn1KH8lG1kcJsggxU5juUVJKwONBpDXpK3F88+mMkj+UNNI8P8z7r6U
7NYeoRhUq3v4sqWiquasTcZtXesEZKztRMp2JoXW4PJ8W/w4iEVutTTQ0R/wFpmo
pdod3o3oWtjHv4JeEydtIqCSKS3TNjQH99R3R4Pc4Jvqt1IE6rpZYAvPZumud6Q1
2fIszAWWy6Ajt2rFO3R8s09xjo9Fq2ui6H4g11IEdzC57pMoBT3H3pRuuwhdZNm0
J/Eo0u1HFJ61Yw3Nt802j7lFmPT0iG96YESB1agQNOY1ycqDjbfulPrqS4o9cKlX
PRsWSBVVnKgJTKyFjsXSRQpDH8qZALHZcTAT8DdCIAjpRNwWAPBUDPcUiYngDJZ/
+jFws/PUOk92PQmndnNNl79dHN/qjppeKtkGumVRLVmRhXOc/OD7ZLKVPVNCzdZe
FRox6i1e63RuqOenOd5AW7WsWBhSyfFgFEWKAOhKHVB58DmzFXaU5TJi4kY9EjpD
mTRSQVFKmxp66ybaXcYW0Dicfn/avk0Uno1eLe4WfiyoVPpcInDFfces5T/xxEyn
i0ExbDdPQEIkV7i1i+4LKk7vsV5RqIgvzF24xjhFeckqjyNunto=
=NuWM
-----END PGP SIGNATURE-----