fix(ssa): Insert checks for possible OOB array accesses during DIE#9280
Conversation
Co-authored-by: Tom French <15848336+TomAFrench@users.noreply.github.com>
Changes to Brillig bytecode sizes
🧾 Summary (10% most significant diffs)
Full diff report 👇
|
Changes to number of Brillig opcodes executed
🧾 Summary (10% most significant diffs)
Full diff report 👇
|
Changes to circuit sizes
🧾 Summary (10% most significant diffs)
Full diff report 👇
|
There was a problem hiding this comment.
⚠️ 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: cbc53e1 | Previous: ad16599 | Ratio |
|---|---|---|---|
sha512-100-bytes |
0.104 s |
0.056 s |
1.86 |
This comment was automatically generated by workflow using github-action-benchmark.
CC: @TomAFrench
There was a problem hiding this comment.
⚠️ 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: cbc53e1 | Previous: ad16599 | Ratio |
|---|---|---|---|
test_report_AztecProtocol_aztec-packages_noir-projects_noir-protocol-circuits_crates_types |
2 s |
1 s |
2 |
This comment was automatically generated by workflow using github-action-benchmark.
CC: @TomAFrench
|
Some last arb tests are failing, currently investigating. |
Co-authored-by: Tom French <15848336+TomAFrench@users.noreply.github.com>
81409f2
into
tf/optimize-array-access-checks
Description
Problem*
Builds off of #9200. Fixes failures and regressions as a result of #9200.
Alternative to #9232
Summary*
I originally had started just working off of #9232 so that is labelled as the parent as to avoid a long commit history. I'm going to transfer this over so that #9200 is the parent.
Brings back logic introduced in #5691 and deleted in #7995. #5691 was originally created to create parity between ACIR/Brillig without having massive regressions. So I thought it made sense to bring back in this scenario no that we no longer want explicit array OOB checks in SSA for ACIR.
Additional Context
Documentation*
Check one:
PR Checklist*
cargo fmton default settings.