Re: Delay in 14.0-RELEASE cycle and blocking items

From: Dimitry Andric <dim_at_FreeBSD.org>
Date: Wed, 03 May 2023 08:40:51 UTC
On 3 May 2023, at 09:53, Alexey Dokuchaev <danfe@FreeBSD.org> wrote:
> 
> On Mon, May 01, 2023 at 06:14:49PM +0000, Glen Barber wrote:
>> ...
>> There is no feasible way we are going to make the branch point of
>> stable/14 in time, with that scheduled for May 12, 2023 with the above
>> points.  That said, this is not an all-inclusive list, but the more
>> major items on our radar at the moment.
> 
> Does this delay mean we might get Clang 16 in the base?  Current 15.0.7
> hits assertion on one of my ports which had allegedly been fixed in 16.
> Also, AFAIU it comes with better support for modern C++, e.g. ranges.

https://bugs.freebsd.org/271047 is the exp-run bug for that; it will
depend on how much ports fallout there is, and the effort required to
fix things. Last time with clang 15 it took quite a while, but I hope it
may be somewhat easier this time.

For now it looks like the most impactful change is the new default of
-std=gnu++17 for C++ mode (like gcc >= 11), since C++17 has actively
removed a bunch of things which were deprecated before, for example the
'register' keyword. That tends to break older software, or software
which isn't updated very often.

-Dimitry