[Bug libgcc/99759] morestack.S should support .init_array.0 besides .ctors.65535

2021-10-08 Thread i at maskray dot me via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99759 Fangrui Song changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug libgcc/99759] morestack.S should support .init_array.0 besides .ctors.65535

2021-04-04 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99759 Andrew Pinski changed: What|Removed |Added Last reconfirmed||2021-04-05 Status|UNCONFIRME

[Bug libgcc/99759] morestack.S should support .init_array.0 besides .ctors.65535

2021-08-11 Thread amodra at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99759 Alan Modra changed: What|Removed |Added CC||amodra at gmail dot com Status|

[Bug libgcc/99759] morestack.S should support .init_array.0 besides .ctors.65535

2021-08-11 Thread i at maskray dot me via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99759 --- Comment #3 from Fangrui Song --- (In reply to Alan Modra from comment #2) > > this means the ctors.65535 will come last. > Nope, it will come first. And since DT_INIT_ARRAY pointers are executed in > the order they appear in the array, it wi