> On 14 Feb 2026, at 17:08, David Malcolm <[email protected]> wrote: > > On Sat, 2026-02-14 at 10:51 -0500, David Malcolm wrote: >> I'd like to push this to trunk now, but I appreciate that it's >> non-trivial and not technically a fix of a regression, but it does >> add >> UX polish. >> >> I can self-approve the diagnostics/json refactorings. >> >> aarch64 maintainers: are the aarch64 changes OK for trunk, either in >> stage 4 or next stage 1?
I’m okay with having this in stage4 for the aarch64 parts. It’s making the first release of the new feature better, and it is a GCC-developer-oriented feature so fixing any hypothetical fallout with backports to the branch is very feasible. Thanks for working on this, Kyrill >> >> Release managers: is this OK for stage 4, or should this wait until >> next >> stage 1? > > Sorry, forgot to say: > > * successfully bootstrapped & regrtested on x86_64-pc-linux-gnu. > * verified make check-gcc RUNTESTFLAGS="aarch64-json-tunings.exp=*" > with --target=aarch64-unknown-linux-gnu > * hand-verified SARIF and HTML output > * hand-verified that valgrind is clean > > Dave >
