-
Notifications
You must be signed in to change notification settings - Fork 152
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 basic support for selecting a codegen backend for compile benchmarks #1742
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Basically seems ok, though I didn't really look at the DB changes because I don't know anything about that.
782fb63
to
adb397d
Compare
Thanks for taking a look, I have resolved the comments. |
adb397d
to
53f5129
Compare
Turns our that |
53f5129
to
60420cd
Compare
Rebased to fix conflict. |
Also removes the `possible_values` implementation. It wasn't used by Clap anyway.
Since we're already modifying the pstat_series table, this commit also renames the cache column to scenario, and the statistic column to metric, to resolve a long-standing mismatch in the terminology.
60420cd
to
83140fb
Compare
Here goes nothing. |
This PR introduces a new parameter for compilation benchmarks - a codegen backend. It adds support for it to the collector and the database. It does not yet modify the web UI, and it also doesn't add other backends than the default one (LLVM).
The database changes will require the most review scrutiny. I tested the DB migration for both SQLite and Postgre locally.
Best reviewed commit by commit.