Ah, okay so that's it. I wasn't specifying a platform. Thanks! But yeah I can imagine performance isn't exacly an easy problem to tackle. For now though just giving it a bunch more threads helps a lot to speed it up across the board, even if Windows still is slower.
I've been doing some comparisons between how cppcheck runs in Windows vs Linux and I noticed that Windows tends to have a few extra errors that are missing from the Linux reports. I'm using 1.8.4 for both. Is this something that's expected? If not and it helps, I can see this happen when running against lighttpd-1.4.49, among others. For Windows I tried both the precompiled binary and my own build which give the same results. On linux I built it using make SRCDIR=build CFGDIR=cfg HAVE_RULES=yes CXXFLAGS="-O2...
I've been doing some comparisons between how cppcheck runs in Windows vs Lunux and I noticed that Windows tends to have a few extra errors that are missing from the Linux reports. I'm using 1.8.4 for both. Is this something that's expected? If not and it helps, I can see this happen when running against lighttpd-1.4.49, among others. For Windows I tried both the precompiled binary and my own build which give the same results. On linux I built it using make SRCDIR=build CFGDIR=cfg HAVE_RULES=yes CXXFLAGS="-O2...
I've been doing some comparisons between how cppcheck runs in Windows vs Lunux and I noticed that Windows tends to have a few extra errors that are missing from the Linux reports. I'm using 1.8.4 for both. Is this something that's expected? If not and it helps, I can see this happen when running against lighttpd-1.4.49, among others. For Windows I tried both the precompiled binary and my own build which give the same results. On linux I built it using make SRCDIR=build CFGDIR=cfg HAVE_RULES=yes CXXFLAGS="-O2...
I've noticed there's some errors that seem to be missing from the --errorlist. - allocaCalled - stlcstrthrow - pureVirtualCall - comparisonOfBoolWithInvalidComparator - invalidScanfFormatWidth_smaller - redundantBitwiseOperationInSwitch - invalidFree As far as I can tell, all of these are run in their respective runChecks/runSimplifiedChecks methods, but arent in getErrorMessages (or for invalidScanfFormatWidth_smaller, where it only has the case to show invalidScanfFormatWidth), so none of them...