https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81084
--- Comment #11 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- Even rs6000 changes related to IEEE long double support are potentially relevant to powerpcspe (not anything related to binary128 in VSX, obviously, but more generic IEEE long double changes). I suspect the support for IEEE long double for 32-bit is pretty bit-rotten (old ABI passing by reference, I think), but logically it's just as meaningful for this port as for rs6000 (and powerpcspe should stay compatible with the soft-float ABI in the rs6000 port). Shared between the ports (so you don't need to do any cleanup there at present for this issue): libgcc code, documentation, testsuite/gcc.target/powerpc. As powerpcspe is neither a primary nor secondary target, you're free to apply non-regression-fix changes as you wish, but it's up to you to have the port in a stable state at the time of branching as any instability of such a port won't be relevant to choosing when to branch for a release.
