[Bug target/114158] Wrong FDPIC special-casing in crtstuff produces invalid pointer in init_array

2024-02-28 Thread bugdal at aerifal dot cx via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114158

--- Comment #5 from Rich Felker  ---
I don't know how I ended up copying the wrong commit id, but the one I meant to
reference was 9c560cf23996271ee26dfc4a1d8484b85173cd12.

Actually, I do know now. I got it out of the gitweb url which gratuitously ahs
the parent hash in a place where it's easy to accidentally copy instead of the
hash of the commit you're viewing (one of the many reasons I prefer cgit):

https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=9c560cf23996271ee26dfc4a1d8484b85173cd12;hp=6bcbf80c6e2bd8a60d88bbcac3d70ffb67f4888f

So indeed, the breakage was detected upstream and worked around, as I said.

[Bug target/114158] Wrong FDPIC special-casing in crtstuff produces invalid pointer in init_array

2024-02-28 Thread jcmvbkbc at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114158

--- Comment #4 from jcmvbkbc at gcc dot gnu.org ---
> It seems to have been realized that this was not working, as
> 6bcbf80c6e2bd8a60d88bbcac3d70ffb67f4888f disabled initfini arrays on 
> ARM/FDPIC,
> but didn't identify the root cause.

I believe that 9c560cf23996271ee26dfc4a1d8484b85173cd12 was meant here.