Thread overview
On the D Blog: Using the GCC Static Analyzer on the D Programming Language
5 days ago
Mike Parker
4 days ago
Dukc
4 days ago
max haughton
3 days ago
Walter Bright
5 days ago

If you saw Max Haughton's DConf Online 2021 presentation (Q & A video coming soon), or followed his remarks here in the forums or the D Community Discord, you know that profiling and static analysis are among his major interests.

The DConf Online video was all about profiling. Now, he's submitted an article to the D Blog showing why the GCC static analyzer is useful for D and how to use it.

The Blog:
https://dlang.org/blog/2022/01/14/using-the-gcc-static-analyzer-on-the-d-programming-language/

Reddit:
https://www.reddit.com/r/programming/comments/s3sh9p/using_the_gcc_static_analyzer_on_the_d/

4 days ago

On Friday, 14 January 2022 at 13:37:11 UTC, Mike Parker wrote:

>

The Blog:
https://dlang.org/blog/2022/01/14/using-the-gcc-static-analyzer-on-the-d-programming-language/

Reddit:
https://www.reddit.com/r/programming/comments/s3sh9p/using_the_gcc_static_analyzer_on_the_d/

Wow, it looks like the analyzer is easy to use! If bloated in it's error messages.

4 days ago

On Friday, 14 January 2022 at 20:25:22 UTC, Dukc wrote:

>

On Friday, 14 January 2022 at 13:37:11 UTC, Mike Parker wrote:

>

The Blog:
https://dlang.org/blog/2022/01/14/using-the-gcc-static-analyzer-on-the-d-programming-language/

Reddit:
https://www.reddit.com/r/programming/comments/s3sh9p/using_the_gcc_static_analyzer_on_the_d/

Wow, it looks like the analyzer is easy to use! If bloated in it's error messages.

Better bloated than bad IMO. You'll notice that the GCC backend can literally do a nicer error message than the D frontend. We should really have these for DIP1000, but the analysis just kind of happens as the compiler sees the code so doing these top-down views is quite hard.

3 days ago
Nice work, Max!