Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: symbolic simulation profiling #165

Closed
ntc2 opened this issue Aug 17, 2016 · 4 comments
Closed

Feature Request: symbolic simulation profiling #165

ntc2 opened this issue Aug 17, 2016 · 4 comments
Labels
type: enhancement Issues describing an improvement to an existing feature or capability
Milestone

Comments

@ntc2
Copy link
Contributor

ntc2 commented Aug 17, 2016

It would be useful to get a timing profile for symbolic simulation: a list of (e.g. LLVM) function names followed by the cumulative (including sub calls) and non cumulative run time. Sorting the results by cumulative time might be a good default. To get other sort orders, we can pipe the output into sort -k <i>,<i>n or whatever.

The best approximation I have right now is running saw -v2 and paying attention to which function names stay on the screen for a long time.

@atomb atomb added the type: enhancement Issues describing an improvement to an existing feature or capability label May 2, 2017
@langston-barrett
Copy link
Contributor

@robdockins @lukemaurer There appears to be some support in Crucible for profiling, can you comment on the status of this issue?

@atomb atomb added this to the 1.0 milestone May 17, 2019
@atomb
Copy link
Contributor

atomb commented May 17, 2019

There's pretty comprehensive support in Crucible, and I think what remains for this issue is mostly a matter of adding the UI to enable it.

@robdockins
Copy link
Contributor

Indeed, it's really just a question of how to expose that functionality to the SAW user.

@langston-barrett
Copy link
Contributor

Looks like this and #364 are duplicates.

brianhuffman pushed a commit that referenced this issue Apr 26, 2021
fix coq import bug (SAWVector.. -> SAWCoreVector..)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement Issues describing an improvement to an existing feature or capability
Projects
None yet
Development

No branches or pull requests

4 participants