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

Have InstructionLifters Attached to Arches Share Operand Lifters #619

Open
2over12 opened this issue Aug 20, 2022 · 0 comments
Open

Have InstructionLifters Attached to Arches Share Operand Lifters #619

2over12 opened this issue Aug 20, 2022 · 0 comments

Comments

@2over12
Copy link
Contributor

2over12 commented Aug 20, 2022

Currently, each instruction lifter attached to an instruction has a different operand lifter, preventing effective use of the operand cache. Potentially, LiftIntoBlock should take a reference to an OperandLifter and InstructionLifter is no longer a subtype of OperandLifter. The point here being that the client manages a single OperandLifter instance for the arch (clearing the cache when needed ie. between functions) and that single operand lifter is passed to all instruction lifters that need to lift operands.

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

No branches or pull requests

1 participant