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

[jcmvbkbc at gcc dot gnu.org via Gcc-bugs]

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

jcmvbkbc at gcc dot gnu.org changed:

   What|Removed |Added

 CC||jcmvbkbc at gcc dot gnu.org

--- Comment #3 from jcmvbkbc at gcc dot gnu.org ---
67b0605494f32811364e25328d3522467aaf0638 is my local fix to the change that was
introduced by the 5d727a4b20257275df59182b00f3bf240772cd0d. I believe that the
changes done in the latter commit to the libgcc/unwind-pe.h and
libstdc++-v3/libsupc++/eh_personality.cc need to be restricted to ARM only, if
needed at all. But that's separate from the crtstuff issue.

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

[pinskia at gcc dot gnu.org via Gcc-bugs]

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

--- Comment #2 from Andrew Pinski  ---
(In reply to Andrew Pinski from comment #1)
> >6bcbf80c6e2bd8a60d88bbcac3d70ffb67f4888f
> 
> that seems unrelated "retain debug stmt order when moving to successors":
> https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;
> h=6bcbf80c6e2bd8a60d88bbcac3d70ffb67f4888f

so I think you mean 67b0605494f32811364e25328d3522467aaf0638 but that never was
committed upstream, it is only in the https://github.com/jcmvbkbc/gcc-xtensa
git repo.

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

[pinskia at gcc dot gnu.org via Gcc-bugs]

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

--- Comment #1 from Andrew Pinski  ---
>6bcbf80c6e2bd8a60d88bbcac3d70ffb67f4888f

that seems unrelated "retain debug stmt order when moving to successors":
https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=6bcbf80c6e2bd8a60d88bbcac3d70ffb67f4888f