Il 26/02/24 02:41, NightStrike ha scritto:
It's mostly up to you whether you want to make the patch and test it.
I mean, the whole file has no code modifications since bd6ecbe48ada (2020), and that specific function is the same since it was first committed (bf1431e3596b, from 2012). I don't think I should make a separate patch for backports: the one I originally posted cherry-picks cleanly even to releases/gcc-4.8.0 (first release containing bf1431e3596b, at least according to git tag --contains), and the caller code is just the same as well, so I expect that technically it could be applied pretty much up to there without any modification.
Now, having a look at https://gcc.gnu.org/releases.html I seem to understand that the current "active" major releases are 11, 12 and 13. I would surely backport to 13, especially given that the patch was developed and tested on that release in first place. 11 and 12 would be nice too, although I made no explicit tests there; a quick check with
git diff releases/gcc-11.1.0 origin/master -- libgcc/unwind.inc libgcc/unwind-seh.c libstdc++-v3/libsupc++/eh_throw.cc
doesn't show any difference that is relevant for my patch. Still, if I find some time for that I could compile these patched releases and see if the patch still works correctly for extra caution.
Matteo
