Skip to content

feat(gpu_prover): [DO NOT MERGE] Stage 3: avoid redundantly computing challenge data and support boundary conditions for multiple init/teardown sets#115

Closed
mcarilli wants to merge 12 commits intoav_backportsfrom
mc-refactor-stage-3-async-data
Closed

feat(gpu_prover): [DO NOT MERGE] Stage 3: avoid redundantly computing challenge data and support boundary conditions for multiple init/teardown sets#115
mcarilli wants to merge 12 commits intoav_backportsfrom
mc-refactor-stage-3-async-data

Conversation

@mcarilli
Copy link

@mcarilli mcarilli commented Sep 6, 2025

Closing in favor of #126.


What ❔

Why ❔

Is this a breaking change?

  • Yes
  • No

Checklist

  • PR title corresponds to the body of PR (we generate changelog entries from PRs).
  • Tests for the changes have been added / updated.
  • Documentation comments have been added / updated.
  • Code has been formatted.

@mcarilli mcarilli changed the title feat(gpu_prover): [WIP] Stage 3: avoid redundantly computing challenge data and support boundary conditions for multiple init/teardown sets feat(gpu_prover): Stage 3: avoid redundantly computing challenge data and support boundary conditions for multiple init/teardown sets Sep 14, 2025
@mcarilli mcarilli changed the title feat(gpu_prover): Stage 3: avoid redundantly computing challenge data and support boundary conditions for multiple init/teardown sets feat(gpu_prover): [DO NOT MERGE] Stage 3: avoid redundantly computing challenge data and support boundary conditions for multiple init/teardown sets Sep 17, 2025
mcarilli added a commit that referenced this pull request Sep 17, 2025
… and support boundary conditions for multiple init/teardown sets (rebase) (#126)

## What ❔

Rebase of #115 onto
`dev`.

## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- The `Why` has to be clear to non-Matter Labs entities running their
own ZK Chain -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Is this a breaking change?
- [ ] Yes
- [ ] No

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [ ] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted.

---------

Co-authored-by: mcarilli <mcarilli@gmail.com>
@mcarilli mcarilli closed this Sep 17, 2025
@mcarilli mcarilli deleted the mc-refactor-stage-3-async-data branch September 17, 2025 17:14
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.

1 participant