@romin
I agree, but on more obscure architectures it often does make sense — gcc and llvm often introduce critical bugs which get fixed in later releases, but never get backported, e.g. clang from llvm15 was segfaulting randomly on my PPC machine — I tried a few patches, including the one that looked very much like it symptoms-wise — all to no success. But with llvm17 it works perfectly again :marseyshrug:
Now Python3.12.2 segfaults right on being launched — I thought it's some weird endian-ness problem due to cross compilcation, so I've built it natively — and it's just as broken. 3.12.1 works fine — I'm simply out of ideas what could've introduced such a bug with a patchlevel update.
With marginal architectures — it's often weird shit like this :marseysigh:
@mona @bronze