8000 Remove range check 3,6 by anatgstarkware · Pull Request #889 · starkware-libs/stwo-cairo · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Remove range check 3,6 #889

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

Merged
merged 2 commits into from
May 22, 2025
Merged

Remove range check 3,6 #889

merged 2 commits into from
May 22, 2025

Conversation

anatgstarkware
Copy link
Contributor
@anatgstarkware anatgstarkware commented May 8, 2025

This change is Reviewable

Copy link
Collaborator
@shaharsamocha7 shaharsamocha7 left a comment

Choose a reason for hiding this comment

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

Reviewed 1 of 14 files at r1, all commit messages.
Reviewable status: 1 of 14 files reviewed, 1 unresolved discussion (waiting on @DavidLevitGurevich)


a discussion (no related file):
Do you think there would be more changes the preprocessed trace?

@anatgstarkware
Copy link
Contributor Author
Previously, shaharsamocha7 wrote…

Do you think there would be more changes the preprocessed trace?

Yes, should I do that in this pr?

@anatgstarkware
Copy link
Contributor Author
Previously, anatgstarkware (anatg) wrote…

Yes, should I do that in this pr?

Done

Copy link
Collaborator
@DavidLevitGurevich DavidLevitGurevich left a comment

Choose a reason for hiding this comment

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

Reviewed 8 of 14 files at r1, 12 of 12 files at r2, all commit messages.
Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @shaharsamocha7)


stwo_cairo_prover/crates/cairo-air/src/components/constraints_regression_test_values.rs line 49 at r2 (raw file):

pub const RANGE_CHECK_BUILTIN_BITS_128: QM31 = qm31!(98318865, 510635574, 1814943674, 477505709);
pub const RANGE_CHECK_FELT_252_WIDTH_27: QM31 = qm31!(82213281, 219376879, 729002900, 792303124);
pub const RANGE_CHECK_6: QM31 = qm31!(1839596244, 1029136098, 314080530, 1911163288);

why did these regressions change too?

@anatgstarkware
Copy link
Contributor Author

stwo_cairo_prover/crates/cairo-air/src/components/constraints_regression_test_values.rs line 49 at r2 (raw file):

Previously, DavidLevitGurevich wrote…

why did these regressions change too?

because I changed them to use Seq preprocessed column

Copy link
Collaborator
@DavidLevitGurevich DavidLevitGurevich left a comment

Choose a reason for hiding this comment

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

:lgtm:

Reviewed 2 of 2 files at r3, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @shaharsamocha7)

Copy link
Collaborator
@shaharsamocha7 shaharsamocha7 left a comment

Choose a reason for hiding this comment

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

Reviewed all commit messages.
Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @anatgstarkware)


stwo_cairo_prover/crates/cairo-air/src/preprocessed.rs line 150 at r3 (raw file):

        Box::new(range_check_19),
        Box::new(range_check_3_6_col_0),
        Box::new(range_check_3_6_col_1),

what's that change?

Code quote:

        Box::new(range_check_6),
        Box::new(range_check_8),
        Box::new(range_check_11),
        Box::new(range_check_12),
        Box::new(range_check_18),
        Box::new(range_check_19),
        Box::new(range_check_3_6_col_0),
        Box::new(range_check_3_6_col_1),

stwo_cairo_prover/crates/cairo-air/src/components/constraints_regression_test_values.rs line 54 at r3 (raw file):

pub const RANGE_CHECK_12: QM31 = qm31!(2029705150, 1702041781, 1878593402, 1237923315);
pub const RANGE_CHECK_18: QM31 = qm31!(160488628, 2118914040, 1869606781, 508250040);
pub const RANGE_CHECK_19: QM31 = qm31!(1263070117, 595729633, 939215182, 505220046);

why all of those were changed?

Code quote:

pub const RANGE_CHECK_6: QM31 = qm31!(1839596244, 1029136098, 314080530, 1911163288);
pub const RANGE_CHECK_8: QM31 = qm31!(619380186, 51892308, 1959448152, 27164417);
pub const RANGE_CHECK_11: QM31 = qm31!(1797671535, 1448714071, 655307656, 610124137);
pub const RANGE_CHECK_12: QM31 = qm31!(2029705150, 1702041781, 1878593402, 1237923315);
pub const RANGE_CHECK_18: QM31 = qm31!(160488628, 2118914040, 1869606781, 508250040);
pub const RANGE_CHECK_19: QM31 = qm31!(1263070117, 595729633, 939215182, 505220046);

Copy link
Collaborator
@shaharsamocha7 shaharsamocha7 left a comment

Choose a reason for hiding this comment

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

:lgtm:

Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on @anatgstarkware)

@anatgstarkware anatgstarkware merged commit e8f6588 into main May 22, 2025
7 checks passed
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.

3 participants
0