added command-line option --valueflow-max-iterations to control amount of valueflow iterations / also log debug warning when iterations are being exceeded - #4557

I have the feeling users would somehow be interested to have different settings for different files. Maybe a user normally wants to have 8 iterations, but then on some files valueflow is a big problem and then the user wants to have a low value for those.

That's possible. But without any data collected in daca we don't even know how many iterations are actually being performed. In our code we don't exceed it - otherwise the selfcheck would have failed.

That's possible. But without any data collected in daca we don't even know how many iterations are actually being performed.

I envision that this will be a large feature that we don't implement quickly.

One possible workflow might be like this:

• User thinks that normal Cppcheck analysis is too slow.
• User runs the full Cppcheck analysis with some additional option; then CPU statistics for each file is generated.
• Using the statistics the user can see how much time all valueflow iterations take. And can get a idea how much time he can save by limiting the number of iterations for certain selected files.
• The user can configure how much valueflow cppcheck will run on each file.

That's possible. But without any data collected in daca we don't even know how many iterations are actually being performed.

I envision that this will be a large feature that we don't implement quickly.

I think that would require a .cppcheck like config file - there's a ticket about that which I could not find.

Starting with actually exposing those tunable and providing feedback is a way too start. We have too many hard-coded things.

Well as a undocumented flag I can allow this.

There is a potential business deal that would make it possible to look considerably into performance. I have no idea when I will know if we get it or not.

Packages which exceed this: http://cppcheck1.osuosl.org:8000/head-valueFlowMaxIterations

I will add it to the main page with some upcoming daca-server PR.

I forgot to provide the filename that experiences this.

I forgot to provide the filename that experiences this.

Fixed in #4664.