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

chore: Skip unrolling loops for Brillig #2587

Closed
wants to merge 1 commit into from

Conversation

kevaundray
Copy link
Contributor

Description

This increases the amount of memory we use and at the moment the compiler doesn't seem to be handling this well.

The tradeoff as discussed with @jfecher is that the mem2reg pass becomes less useful.

Problem*

Resolves

Summary*

Documentation

  • This PR requires documentation updates when merged.

    • I will submit a noir-lang/docs PR.
    • I will request for and support Dev Rel's help in documenting this PR.

Additional Context

PR Checklist*

  • I have tested the changes locally.
  • I have formatted the changes with Prettier and/or cargo fmt on default settings.


// We abort on error if the runtime is Acir, because ACIR does not
// know how to handle loops even with constant bounds.
let abort_on_error = function_runtime == RuntimeType::Acir;
Copy link
Contributor Author

Choose a reason for hiding this comment

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

left this in here, though it should always be true

@kevaundray
Copy link
Contributor Author

forgot to merge this, I like Jake's comments better so closing this in favour of #2590

@kevaundray kevaundray closed this Sep 7, 2023
@TomAFrench TomAFrench deleted the kw/dont-unroll-brillig-loops branch November 20, 2024 12:01
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