https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119324
--- Comment #8 from Robert Dubner <rdubner at gcc dot gnu.org> --- I don't like making blind changes. I need to duplicate the report you created so that I know that any changes I make actually fix cppcheck outputs without creating new ones. The "problems" reported by Cppcheck are not causing any difficulties that I am aware of. Certainly the various test suites are all succeeding with those problems in place. Jim has repaired some of them. I don't know which. The source code has changed significantly since you first posted about it, so I can't be sure about line numbers. So, in order for cppcheck to be useful, especially in the face of its extensive configurability, what I find to be Cppcheck's sketchy documentation, and my current complete ignorance of how to use it, it would be very useful for me to know exactly how you are using it as a starting point. I guess I am asking you to treat it like a bug report. If Cppcheck .cfg files have been created for coping with GCC source code fiels, I would appreciate knowing what they are. There must be complete command lines for running cppcheck and for grepping the result; I need to know what those are. Because right now I can't seem to make it work at all. I regard learning how to use Cppcheck in a way consistent with what you have developed as at least as important as making stylistic changes about clarifying operator precedence.
