-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add performance testing #5
Comments
Some initial results, showing 50 slowest compiles, and what analyzer item took longest for each one:
|
davidmalcolm
added a commit
that referenced
this issue
Jul 31, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should probably check how much time taken is by the analyzer.
My goal is that the analyzer should "merely" double the compile time.
Perhaps express time taken by analyzer as a multiple of time taken by the rest of the compile; group files by the multiple?
Probably should add absolute and comparison report scripts for this
I've filed https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109361 with GCC to track adding profiling information to the SARIF files
The text was updated successfully, but these errors were encountered: