https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78352
--- Comment #24 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to Sergey Fedorov from comment #23) > (In reply to Andrew Pinski from comment #22) > > (In reply to Sergey Fedorov from comment #21) > > > Any chance of having it fixed in gcc14? > > > > It is too late to be included in GCC 14, GCC is in stage 3 already, that is > > no new features can be included that was not posted before a specific date. > > See https://gcc.gnu.org/pipermail/gcc/2023-November/242898.html and > > https://gcc.gnu.org/develop.html about the timing there. > > Oh… > > Can new features be added into minor releases, like 14.x? No. The general rule is that we only fix regressions and documentation/tests on release branches. As Darwin maintainer, I include fixes for build/ABI problems in back-ports (where they only effect Darwin). Any new feature like blocks support would be much more invasive than that, so definitely have to wait for GCC-15. Like other "vendors", I maintain external branches for Darwin that have more relaxed rules - allowing port-critical back ports that would not be acceptable upstream, However, first we have to complete this work and bring it forward to trunk .. then we can worry about back ports to older branched ;)
