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

fix: EcDoubleChip dummy row #1239

Merged
merged 1 commit into from
Jan 19, 2025
Merged

fix: EcDoubleChip dummy row #1239

merged 1 commit into from
Jan 19, 2025

Conversation

jonathanpwang
Copy link
Contributor

We need the dummy row to have is_valid=0, is_double=0. Previously we did this by duplicating the first row. However when the same chip is used across continuation segments, the first row might not be setup. So now we explicitly generate the dummy row to have the above properties.

Copy link

group app.proof_time_ms app.cycles app.cells_used leaf.proof_time_ms leaf.cycles leaf.cells_used
verify_fibair (+24 [+0.7%]) 3,415 711,313 25,519,644 - - -
fibonacci_program (+60 [+1.0%]) 6,143 1,500,137 51,505,102 - - -
regex_program (-156 [-0.8%]) 18,759 4,190,904 165,028,173 - - -
ecrecover_program (+15 [+0.6%]) 2,614 285,401 15,092,297 - - -

Commit: 2bd377c

Benchmark Workflow

@jonathanpwang jonathanpwang merged commit c4d81ff into main Jan 19, 2025
16 checks passed
@jonathanpwang jonathanpwang deleted the fix/ec-double-dummy-row branch January 19, 2025 17:45
let mut row = vec![F::ZERO; adapter_width + core_width];
let core_row = &mut row[adapter_width..];
// We **do not** want this trace row to update the range checker
// so we must create a temporary range checker
Copy link
Contributor

Choose a reason for hiding this comment

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

🧠

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants