Skip to content
This repository has been archived by the owner on Aug 15, 2024. It is now read-only.

Fix naive range checks in bigint_new #45

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

tim-becker
Copy link

@tim-becker tim-becker commented Mar 12, 2023

We noticed a few bugs with the naive strategy for range checks:

  1. The code assumed the wrong bit order fromBitIterator
  2. In the fast case (num_bits < 4), the linear combination check wasn't actually being enforced
  3. In the other case, d_next_coeff was being updated incorrectly.

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

Successfully merging this pull request may close these issues.

1 participant