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

Upgrade Rust toolchain to 2023-08-14 #2688

Merged
merged 1 commit into from
Aug 16, 2023

Conversation

zhassan-aws
Copy link
Contributor

Description of changes:

Relevant upstream commits/PRs:

rust-lang/rust#114382: this required handling the new compare_bytes intrinsic

rust-lang/rust#114622: crate_types is no longer a method in Session

Resolved issues:

Resolves #ISSUE-NUMBER

Related RFC:

Optional #ISSUE-NUMBER.

Call-outs:

Testing:

  • How is this change tested? Current regressions

  • Is this a refactor change? No

Checklist

  • Each commit message has a non-empty body, explaining why the change was made
  • Methods or procedures are documented
  • Regression or unit tests are included, or existing tests cover the modified code
  • My PR is restricted to a single feature or bugfix

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

@zhassan-aws zhassan-aws added the Z-BenchCI Tag a PR to run benchmark CI label Aug 16, 2023
@zhassan-aws zhassan-aws requested a review from a team as a code owner August 16, 2023 03:28
Copy link
Member

@tautschnig tautschnig left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems the fmt_i8 test is now taking substantially longer, but perhaps not in a surprising way: this test also has an change in the number of instructions. Perhaps this exercises the new intrinsic? IMHO ok to accept this performance change.

@zhassan-aws
Copy link
Contributor Author

I'm a bit confused about the fmt_i8 test because in #2576, it was reported that its verification time increased from ~6s to 10 minutes. Looks like the time went down at some point, and then went up again with this toolchain upgrade? The increase is not as substantial as before though as it only went up to ~44 seconds (and solver runtime went up to ~19 seconds).

@celinval do you have any more information on the performance trend of this test?

@zhassan-aws
Copy link
Contributor Author

Ah, looks like changing the default solver to cadical brought down the time from ~1059 seconds to ~42 seconds:

https://github.com/model-checking/kani/actions/runs/5744858062

But based on the perf-benchcomp action runs, there is some variance in the runtime of this benchmark, so we can safely ignore the increase in runtime seen on this PR.

@zhassan-aws zhassan-aws merged commit 9f30699 into model-checking:main Aug 16, 2023
@zhassan-aws zhassan-aws deleted the toolchain-2023-08-14 branch August 16, 2023 16:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Z-BenchCI Tag a PR to run benchmark CI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants