New features in GCC 16: Improved error messages and SARIF output (developers.redhat.com)
118 points by siteshwar 3 days ago
account42 8 hours ago
I'm unsure if the error message change is actually a good thing. IME the main problem with template error messages is not that they are unreadable but just the sheer amount of them you can get from a simple error which makes it hard to find the root cause among the log spam - making the trace even more verbose will not help that.
bluGill 3 hours ago
Yeah, the example was trivially short. Only one candidate that didn't match. Last time I had a template error the complete compiler output was too large for my scroll back buffer. (4-5 errors, but each repeated in dozens of places). I really want to see the difference in more realistic cases.
NooneAtAll3 2 hours ago
why does this page spam page history with redirects to itself?
https://developers.redhat.com/articles/2026/04/28/gcc-16-imp...
https://developers.redhat.com/articles/2026/04/28/gcc-16-imp...
https://developers.redhat.com/articles/2026/04/28/gcc-16-imp...
ChristianJacobs 11 hours ago
Great news! As someone who's moving back to a C++ job after having worked with Rust for several years now, the error message parsing is one of the things I've been dreading the most... I'm still dreading it, but now sliiightly less.
Also, that interactive `-fanalyze`-output with the pointer visualisation looks super handy!
Happy to see there's still focus on the DX in GCC. C and C++ sorely needs it.
vlovich123 11 hours ago
This has appeared multiple times over the years as “compiler improves c++ errors” and is even the reason given as motivating things like concepts. Sure it keeps improving but the errors don’t seem to actually get smaller. The problem is inherent to templates - c++ got it wrong by having templates start weakly typed and it has no mechanisms to correct it in the language - concepts helped but didn’t definitively fix it and also are a serious level of complexity (ie for writing and defining concepts) - it just shifted the burden one level but ultimately the mess is still there.
After more than 20 years in c++, I gave up that the situation will ever really be fixed vs constantly being made better at the margins, but not as fast as new ideas get added to the language.
ChristianJacobs 11 hours ago
You're not wrong there. The late stage (compilation wise) of template instantiation doesn't help either, as so much context has been built up. The art of debugging C++ compiler output is knowing which 90% to ignore. If you read it all you'll simply go mad.
Concepts at least tells you which criteria you didn't satisfy (as long as the concept is correct...), which - admittedly - feels like putting a bandaid on bullet wound.
estebank 6 hours ago
pjmlp 11 hours ago
Davidbrcz 9 hours ago
pjmlp 11 hours ago
The problem isn't C++, the problem is that the meagre resources those teams have available, rather spend their time catching up to ISO C and ISO C++, than improving error messages.
Hence why SARIF has seen big adoption, as they hope that by exposing that , there are others ways to have others have tools that process SARIF.
ramon156 8 hours ago
While the new error message pinpoints the location of the error better, you have to dig through so much text to find it. Why not have a verbose mode that you can turn off so you only get the last trace of the error message? clippy does this so well, plus you get a suggested fix
gpderetta 5 hours ago
SARIF is machine readable. An editor (or a shell filter if you prefer it that way) would allow hierarchically inspecting the output at the desired detail level. The article shows nested overload candidates that could be potentially be collapsed, for example.
IshKebab 9 hours ago
Wow I never thought I'd see GCC innovating with error messages!
I looked into using SARIF once before and found it's an enormous over-engineered design-by-committee spec, but I guess it's still better than regexes (do people really do that?).
whimblepop 10 minutes ago
SARIF is kinda nice for security-oriented linters imo, since lots of tools know how to speak it. It avoids lock-in that way, which is otherwise/previously pretty common, with every scanning tool using its own bespoke format.
rwmj 4 hours ago
GCC has been innovating for a while with dmalcolm's -fanalyzer stuff.
pjmlp 8 hours ago
So far it seems the best experience that we can kind of have is with VC++, because they use it on the errors section and you can kind of graphically navigate it, however the overall experience is still not out of this world.
crest 5 hours ago
If you want to know how bad it take your time with GCC 4.x before they responded to clang. GCC error messages used to be horrible for anything but the most trival errors. A single C++ template error could span multiple screens and still not tell you the location.