Skip to content

Conversation

@sashass1315
Copy link

  • Fix cairo1-run to use Cairo1RunConfig.relocate_mem and trace_enabled in runner.relocate(...) instead of unconditionally relocating both memory and trace.
  • This change brings Cairo1-run behavior in line with the Cairo 0.x runner, matches CLI expectations (trace/memory requested ⇒ relocate), and avoids unnecessary relocation work.

@JulianGCalderon
Copy link
Contributor

Hi @sashass1315, thanks for the contribution! Left you a small comment. Also, format seems to be failing.

Co-authored-by: Julian Gonzalez Calderon <gonzalezcalderonjulian@gmail.com>
Copy link
Collaborator

@gabrielbosio gabrielbosio left a comment

Choose a reason for hiding this comment

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

Left a small suggestion. Also please fix the linter job.


#### Upcoming Changes

* fix: honor relocate_mem and trace_enabled flags on cairo1-run [#2241](https://github.com/lambdaclass/cairo-vm/pull/2241)
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think the term 'honor' here might sound a bit confusing:

Suggested change
* fix: honor relocate_mem and trace_enabled flags on cairo1-run [#2241](https://github.com/lambdaclass/cairo-vm/pull/2241)
* fix: Make cairo1-run to conditionally relocate memory and trace [#2241](https://github.com/lambdaclass/cairo-vm/pull/2241)

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