dmalcolm

6 ms·

1. 1.▲
   Improvements to errors and warnings in GCC 16(developers.redhat.com)

   6 points by dmalcolm 5mo ago|0 comments
2. 2.▲
   Usability Improvements in GCC 15(developers.redhat.com)

   259 points by dmalcolm 1y ago|223 comments
3. 3.▲
   by dmalcolm 3y ago

   Good point. I took a look, and it appears I hardcoded it, rather than going through our normal color management. Sorry about that. I've filed https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114588 about this and I&
4. 4.▲
   by dmalcolm 3y ago

   Thanks! More details here: https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Format... I hope my choices here work well on a wide variety of terminals.
5. 5.▲
   by dmalcolm 3y ago

   FWIW I implemented SARIF output in GCC 13, which gives a machine-readable interchange format for the errors. It's viewable by e.g. VS Code (via a plugin). Hopefully that makes it easier to grok the messages. You can see an example of
6. 6.▲
   by dmalcolm 3y ago

   FWIW I implemented SARIF output in GCC 13 which is viewable by e.g. VS Code (via a plugin) - though the ASCII art isn't. You can see an example of the output here: https://godbolt.org/z/aan6Kfxds (that's th
7. 7.▲
   Improvements to static analysis in GCC 14(developers.redhat.com)

   396 points by dmalcolm 3y ago|143 comments
8. 8.▲
   Improvements to static analysis in the GCC 13 compiler(developers.redhat.com)

   3 points by dmalcolm 3y ago|0 comments
9. 9.▲
   Static Analysis in GCC 10(developers.redhat.com)

   8 points by dmalcolm 7y ago|0 comments
10. 10.▲
    Usability Improvements in GCC 9(developers.redhat.com)

    15 points by dmalcolm 8y ago|0 comments
11. 11.▲
    by dmalcolm 9y ago

    Thanks; I like that idea. I've filed it as: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84920
12. 12.▲
    by dmalcolm 9y ago

    Thanks; I like it. I've added that to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84890
13. 13.▲
    by dmalcolm 9y ago

    Indeed, dealing with multiple configurations with lots of dependencies is hard. I looked in the option metadata for our C/C++ frontends and -Wduplicated-branches isn't flagged as RejectNegative, so -Wno-duplicated-branches ou
14. 14.▲
    by dmalcolm 9y ago

    Thanks! I've added the idea to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84889
15. 15.▲
    by dmalcolm 9y ago

    Hi Jordi! libgccjit is in maintenance mode: I believe it has everything you need if you (or someone else) wants to implement a JIT for GNU Octave (or for any other interpreter)- I just don't want to be the person to do that, as I have
16. 16.▲
    by dmalcolm 9y ago

    Thanks - a few other people pointed this out, and I agree. I've filed this one as: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84887 and hope to fix it in gcc 9.
17. 17.▲
    by dmalcolm 9y ago

    [author of the blog post here] Sadly, gcc 8 isn't smart enough to do that yet; I only implemented it for simple "return name_of_field;" accessors. But it's an interesting idea, which I've filed as: https:/&#x2
18. 18.▲
    by dmalcolm 9y ago

    Thanks, that would indeed break up the "wall of text" effect. I've filed this along with some related ideas as https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84889 (I hope to improve this in gcc 9)
19. 19.▲
    by dmalcolm 9y ago

    Thanks! Any ideas for other improvements? (even if it's just fixing "paper cut"-style little annoyances)
20. 20.▲
    by dmalcolm 10y ago

    [author of the post] Thanks for the links; a lot of interesting material in there. FWIW, DejaGnu gives some flexibility over how granular the test files can be. For example, here's part of the test case for the -Wmisleading-indentatio
21. 21.▲
    by dmalcolm 10y ago

    It seems to be working again. Sorry about the snafu. I've been exchanging emails with the team on the hosting side, but I don't yet have info on what happened.
22. 22.▲
    by dmalcolm 10y ago

    [author of the article] The RTL dump format does look a lot like Lisp, FWIW; see: https://gcc.gnu.org/onlinedocs/gccint/RTL.html or this article I wrote a while back on it: http://developerblog.redhat.c
23. 23.▲
    by dmalcolm 10y ago

    [author of the post here] Thanks; am chasing it up at my end
24. 24.▲
    by dmalcolm 10y ago

    [author of the post here] Correct: loading the IR dumps back in is new.
25. 25.▲
    by dmalcolm 10y ago

    [author of the post here] Yes: memory management in the compiler is interesting. There's a complicated graph of pointer references. Most of the time the compiler is building something relatively small, so we don't need to bothe
26. 26.▲
    Testing GCC(developers.redhat.com)

    84 points by dmalcolm 10y ago|39 comments
27. 27.▲
    GCC 6: -Wmisleading-indentation vs. “goto fail;”(developerblog.redhat.com)

    199 points by dmalcolm 11y ago|165 comments
28. 28.▲
    Automatically detecting reference-count bugs in Python extension modules(dmalcolm.livejournal.com)

    2 points by dmalcolm 15y ago|0 comments