Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

ethereum / evmone Public

Notifications You must be signed in to change notification settings
Fork 298
Star 883

Code
Issues 66
Pull requests 50
Discussions
Actions
Projects
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Projects
Security
Insights

Optimize Baseline interpreter by using padded code#315

Merged

chfast merged 4 commits intomasterethereum/evmone:masterfrom baseline_padded_codeethereum/evmone:baseline_padded_codeCopy head branch name to clipboard

Jun 4, 2021

+62-46

Conversation Commits4 (4)Checks Files changed

Commits

Commits on Jun 4, 2021

baseline: Copy and pad the code before execution
chfast
committed
baseline: Use padded code for execution
chfast
committed
baseline: Use "infinite" interpreter loop
chfast
committed
baseline: Do not check for out-of-buffer push load
chfast
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.