Support scanning for existing json files

[xzxzzxzxzca]

It would be nice to have an option to just start the tool on an existing collection of profiling files in the build directory instead of capturing them only between the start/stop cycle. Current workflow does not play well with incremental builds where most of the sources may be already processed with their build time stats already captured. In order to use the clang's profiling information one has to always start the build from scratch which doesn't seem to be strictly necessary.

[ben-craig]

There is a way to do this, though it isn't documented. Starting the analyzer generates a file with a time stamp. You can set the time stamp to zero, and then stop will look at all available json files.

…

On Sun, May 3, 2020, 12:40 PM xzxzzxzxzca ***@***.***> wrote: It would be nice to have an option to just start the tool on an existing collection of profiling files in the build directory instead of capturing them only between the start/stop cycle. Current workflow does not play well with incremental builds where most of the sources may be already processed with their build time stats already captured. In order to use the clang's profiling information one has to always start the build from scratch which doesn't seem to be strictly necessary. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#46>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHBSBQQHVKEER3GT46QVRTRPWT7XANCNFSM4MYG6JHA> .

[xzxzzxzxzca]

You can set the time stamp to zero, and then stop will look at all available json files.

Thanks! That's an interesting workaround, seems usable enough.
Although, I still wish there would be a straightforward and more "official" to do this rather trivial task :)

[aras-p]

Added --all mode with #47