MM <finjulhich at gmail.com> writes: > I see gcc 16 erroring with this [...] Yes, we are aware and it's already fixed for the upcoming 2.6.0 (still a few months out).