https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120870
--- Comment #14 from Sam James <sjames at gcc dot gnu.org> --- (In reply to Sam James from comment #13) > It looks like the last commit this machine built python3.14t at was > r16-1594-gb03e0d69b37f6e which predates preserve_none being added > (r16-1692-g9804b23198b39f). > > We had a similar problem in PR120840. (i.e. I've not bisected it but I'm fairly sure it's just because preserve_none is now available and is used.)