https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119324
--- Comment #9 from David Binderman <dcb314 at hotmail dot com> --- (In reply to Robert Dubner from comment #8) > Jim has repaired some of them. I don't know which. See comment 1. > 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. gcc $ find trunk/gcc/cobol/ -name \*.cc -print | sort > file.list gcc $ wc -l file.list 14 file.list gcc $ cppcheck --version Cppcheck 2.17.1 gcc $ (date; cppcheck --enable=all --force --language=c++ `cat file.list`;date) > cppcheck.out 2>&1 gcc $ grep passedByValue cppcheck.out trunk/gcc/cobol/copybook.h:133:34: performance: Function parameter 'input' should be passed by const reference. [passedByValue] trunk/gcc/cobol/exceptg.h:77:56: performance: Function parameter 'files' should be passed by const reference. [passedByValue] trunk/gcc/cobol/inspect.h:203:62: performance: Function parameter 'oper' should be passed by const reference. [passedByValue] gcc $ grep clarifyCalculation cppcheck.out gcc $ grep identicalInnerCondition cppcheck.out gcc $ Exact enough ? That's from recent sources in the last 24 hours or so.
