Track metrics for core and std crates, add loop metrics
#258
Conversation
The crate that we compute metrics for is now configurable when invoking `kani_std_analysis.py`. Should we find a need for further crates beyond `core` or `std` we just need to invoke it more times.
tautschnig
changed the title
core and std cratescore and std cratess, add loop metrics
|
We might want #261 to be merged first and we need model-checking/kani#3915 to be merged. |
carolynzech
changed the title
core and std cratess, add loop metricscore and std crates, add loop metrics
|
This is now working as expected, see tautschnig#11. |
This reverts commit 9c5e56a.
Thank you for catching this! (This is now fixed.)
With the data from tautschnig#11 we get the following for the
And for the
I believe these match expectations. |
The purple entry in the legend on the first graph looks off? But otherwise LGTM |
|
Fixed by adding a missing comma. Now it looks better:
|
9aa99c3
The crate that we compute metrics for is now configurable when invoking
kani_std_analysis.py. Should we find a need for further crates beyondcoreorstdwe just need to invoke it more times.We are now also reporting loop/no-loop information across all the kinds of functions we are tracking as metrics.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.