-
Notifications
You must be signed in to change notification settings - Fork 370
fix(ssa): Keep store whose address is used even after flattening #11380
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
base: master
Are you sure you want to change the base?
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.
⚠️ Performance Alert ⚠️
Possible performance regression was detected for benchmark 'Test Suite Duration'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.
| Benchmark suite | Current: 1bb5312 | Previous: 13ce5c8 | Ratio |
|---|---|---|---|
test_report_zkpassport_noir_rsa_ |
2 s |
1 s |
2 |
This comment was automatically generated by workflow using github-action-benchmark.
CC: @TomAFrench
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.
⚠️ Performance Alert ⚠️
Possible performance regression was detected for benchmark 'Compilation Time'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.
| Benchmark suite | Current: 1bb5312 | Previous: 13ce5c8 | Ratio |
|---|---|---|---|
private-kernel-inner |
2.982 s |
2.386 s |
1.25 |
This comment was automatically generated by workflow using github-action-benchmark.
CC: @TomAFrench
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.
⚠️ Performance Alert ⚠️
Possible performance regression was detected for benchmark 'Execution Time'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.
| Benchmark suite | Current: 1bb5312 | Previous: 13ce5c8 | Ratio |
|---|---|---|---|
sha512-100-bytes |
0.083 s |
0.055 s |
1.51 |
This comment was automatically generated by workflow using github-action-benchmark.
CC: @TomAFrench
|
|
||
| Store { .. } => should_remove_store(function, flattened), | ||
| Store { address, .. } => { | ||
| should_remove_store(function, flattened) && !used_values.contains(address) |
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.
Looks like !used_values.contains(address) should be added to should_remove_store since it is now a condition on us removing the store or not
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.
should_remove_store is a free function also used in the DIE post check so that is why I did not do this change. I could expand its definition to accept used_values though. Do you prefer that?
Description
Problem
Resolves https://github.com/noir-lang/noir/security/advisories/GHSA-pgh4-36hc-pmrx
Summary
Changes:
Additional Context
User Documentation
Check one:
PR Checklist
cargo fmton default settings.