> Am 15.01.2026 um 17:29 schrieb Jose E. Marchesi <[email protected]>:
>
>
> Is it ok to add the bpf-vmtest-tool to contrib/ ?
Sure
> https://gcc.gnu.org/pipermail/gcc-patches/2026-January/705886.html
>
> The other changes are all within BPF specific directories. The change
> to gcc/Makefile.in is not needed because the board should be in dejagnu,
> not GCC.
>
>
>>>> Am 13.01.2026 um 18:24 schrieb David Malcolm <[email protected]>:
>>>
>>> On Mon, 2026-01-12 at 13:01 +0100, Richard Biener wrote:
>>>> Status
>>>> ======
>>>>
>>>> The development trunk is now in Stage 4 of the development of GCC 16.
>>>> Stage 4 allows for regression and documentation fixing, it is
>>>> supposed
>>>> to stabilize trunk for the release of GCC 16.1. Features not merged
>>>> until
>>>> now have to wait for Stage 1 unless you get approval from release
>>>> managers.
>>>
>>> I'd like to merge these UX improvements to error-handling in the C++
>>> FE, which Jason has approved:
>>>
>>> [PATCH 1/2 v2] c++: use nesting and counts in print_candidates
>>> https://gcc.gnu.org/pipermail/gcc-patches/2026-January/705503.html
>>>
>>> [PATCH 2/2 v3] c++: UX improvements for close matches in
>>> print_candidates
>>> https://gcc.gnu.org/pipermail/gcc-patches/2026-January/705618.html
>>>
>>> OK for trunk now, from a release manager perspective?
>>
>> Ok
>>
>> Richard
>>
>>> I believe they are relatively low risk, in that they're just on the
>>> error-handling path.
>>>
>>> Thanks
>>> Dave
>>>
