Uh oh!
There was an error while loading. Please reload this page.
added environment variable UNUSEDFUNCTION_ONLY to make sure only the unusedFunction check is being executed - #4362
Conversation
unusedFunction checkUNUSEDFUNCTION_ONLY hack to only perform the unusedFunction checkdd66980 to
da6273eCompareda6273e to
28c4139CompareUNUSEDFUNCTION_ONLY hack to only perform the unusedFunction checkUNUSEDFUNCTION_ONLY to make sure only the unusedFunction check is being executeddanmar
commented
Aug 20, 2022
This seems to be a quick and small hack of the interface. I don't want small hacks in the interface. A bigger picture is wanted. There should be a consistent way to enable/disable all checks. |
firewave
commented
Aug 20, 2022
This is just temporary and I have an approach to fix this more appropriately. The ground work and approach is easily implemented. But to get it completely fixed will involve a lot of work and will take quite a while. It's also not an "interface" and is not documented at all. |
danmar
commented
Aug 20, 2022
ok. |
firewave
commented
Sep 23, 2022
This is to also speed up the callgrind test proposed in #2944. I will elaborate on steps to get rid of this hack soon. |
firewave
commented
Sep 27, 2022
This reduces Ir from |
firewave
commented
Sep 27, 2022
Not calling the unnecessary |
28c4139 to
30dfd56Compare30dfd56 to
a3ee16cCompare
This is to avoid unnecessary checks being performed as well as speeding up things. See https://trac.cppcheck.net/ticket/10648 and https://trac.cppcheck.net/ticket/10727.