Skip to content

LEVM: Optimize the way valid jump destinations are stored and retrieved #2993

@SDartayet

Description

@SDartayet

Currently, a lot of the time spent in call opcodes is spent either storing the return address as a valid jump destination, or retrieving the valid jump destinations for the destination contract. We might benefit from looking at a faster datastructure that can handle these operations quicker.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions