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

Align on the caching design choice #28

Open
patacca opened this issue Mar 14, 2024 · 0 comments
Open

Align on the caching design choice #28

patacca opened this issue Mar 14, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@patacca
Copy link
Collaborator

patacca commented Mar 14, 2024

We should enforce on the python API the same deisgn choices over caching/uncaching that we used on python-binexport/qbindiff.

The design choices can be summarized in the following points:

  • Function objects are eagerly loaded in the constructor of Program and never deallocated
  • BasicBlock objects are not cached by default. In order to access them in a cached way there are two ways: either with the context manager (with statement) or by manually calling Function.preload() and Function.unload() methods.
  • Everything below basic block will be cached by default (Instruction, Operands, ...)
@patacca patacca added the enhancement New feature or request label Mar 14, 2024
@patacca patacca self-assigned this Mar 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant