Skip to content

feat(gpu): KS32 - Part 2 - Add support for 32b LWE inputs to 64b PBS #3104

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.

Sign up for GitHub

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

Jump to bottom
Open
andrei-stoian-zama wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat(gpu): KS32 - Part 2 - Add support for 32b LWE inputs to 64b PBS #3104

andrei-stoian-zama wants to merge 1 commit into from

Conversation

@andrei-stoian-zama
Copy link
Contributor

@andrei-stoian-zama andrei-stoian-zama commented Dec 10, 2025 •
edited
Loading

  • adds template datatypes for the LWE inputs to the PBS
  • adds a test for k32->PBS
  • adds benchmarking of k32->PBS

@cla-bot cla-bot bot added the cla-signed label Dec 10, 2025
@andrei-stoian-zama andrei-stoian-zama changed the base branch from main to as/ks32_gpu_2 December 10, 2025 11:02
@andrei-stoian-zama andrei-stoian-zama force-pushed the as/ks32_gpu_2 branch 9 times, most recently from f27b770 to 0158140 Compare December 12, 2025 14:53
@andrei-stoian-zama andrei-stoian-zama changed the title feat(gpu): Add support for 32b LWE inputs to 64b PBS feat(gpu): KS32 - Part 2 - Add support for 32b LWE inputs to 64b PBS Dec 12, 2025
Base automatically changed from as/ks32_gpu_2 to main December 12, 2025 21:01
@zama-bot zama-bot removed the approved label Dec 18, 2025
@zama-bot zama-bot removed the approved label Dec 18, 2025
@andrei-stoian-zama andrei-stoian-zama marked this pull request as ready for review December 22, 2025 14:52
@zama-bot zama-bot removed the approved label Jan 5, 2026
@github-actions
Copy link

github-actions bot commented Jan 15, 2026

❌ Milestone Missing

Please assign a milestone to this pull request. If your PR targets the next version of TFHE-rs please use the current quarter milestone, e.g. "Q1 26".
If your PR targets a patch version for previous releases: consider creating a dedicated milestone e.g. v1.5.1 if it does not exist yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@guillermo-oyarzun guillermo-oyarzun Awaiting requested review from guillermo-oyarzun

@soonum soonum Awaiting requested review from soonum soonum is a code owner

@agnesLeroy agnesLeroy Awaiting requested review from agnesLeroy agnesLeroy is a code owner

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

cla-signed

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@andrei-stoian-zama @zama-bot @guillermo-oyarzun