Skip to content

Analyze opcode table #5796

@Arkenan

Description

@Arkenan

We currently have an opcode table in LEVM to redirect from opcode to implementation. We don't know if this is a jump or a call table internally. We need to make that analysis and, in case we are using a call table, evaluate using a jump table and see if we observe improvements.

Metadata

Metadata

Assignees

Labels

levmLambda EVM implementationperformanceBlock execution throughput and performance in general

Type

No type

Projects

Status

No status

Status

Todo

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions