Skip to content

fix(core/vm): trace before memory expansion #31074#2294

Open
gzliudan wants to merge 1 commit intoXinFinOrg:dev-upgradefrom
gzliudan:simplify-interpreter-loop
Open

fix(core/vm): trace before memory expansion #31074#2294
gzliudan wants to merge 1 commit intoXinFinOrg:dev-upgradefrom
gzliudan:simplify-interpreter-loop

Conversation

@gzliudan
Copy link
Copy Markdown
Collaborator

@gzliudan gzliudan commented Apr 9, 2026

Proposed changes

Move opcode tracing out of the dynamic gas branch so tracing always runs before memory expansion. Keep memory resizing in one place to match the upstream interpreter flow.

Ref: ethereum#31074

Types of changes

What types of changes does your code introduce to XDC network?
Put an in the boxes that apply

  • build: Changes that affect the build system or external dependencies
  • ci: Changes to CI configuration files and scripts
  • chore: Changes that don't change source code or tests
  • docs: Documentation only changes
  • feat: A new feature
  • fix: A bug fix
  • perf: A code change that improves performance
  • refactor: A code change that neither fixes a bug nor adds a feature
  • revert: Revert something
  • style: Changes that do not affect the meaning of the code
  • test: Adding missing tests or correcting existing tests

Impacted Components

Which parts of the codebase does this PR touch?
Put an in the boxes that apply

  • Consensus
  • Account
  • Network
  • Geth
  • Smart Contract
  • External components
  • Not sure (Please specify below)

Checklist

Put an in the boxes once you have confirmed below actions (or provide reasons on not doing so) that

  • This PR has sufficient test coverage (unit/integration test) OR I have provided reason in the PR description for not having test coverage
  • Tested on a private network from the genesis block and monitored the chain operating correctly for multiple epochs.
  • Provide an end-to-end test plan in the PR description on how to manually test it on the devnet/testnet.
  • Tested the backwards compatibility.
  • Tested with XDC nodes running this version co-exist with those running the previous version.
  • Relevant documentation has been updated as part of this PR
  • N/A

Copilot AI review requested due to automatic review settings April 9, 2026 07:43
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Apr 9, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 2d22a99d-22ea-46d8-8e43-cf7422b0ac87

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adjusts the EVM interpreter loop in core/vm to make tracer hook invocation flow match upstream more closely by moving opcode tracing out of the dynamicGas branch while keeping memory resizing centralized.

Changes:

  • Hoists memorySize calculation state outside the dynamicGas block.
  • Invokes OnGasChange/OnOpcode tracing in a single unified location.
  • Performs mem.Resize(memorySize) in one place after tracing, preserving “trace before expansion” ordering.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Move opcode tracing out of the dynamic gas branch so tracing always runs before memory expansion.
Keep memory resizing in one place to match the upstream interpreter flow.
@gzliudan gzliudan force-pushed the simplify-interpreter-loop branch from f029f16 to fa830e3 Compare April 9, 2026 07:48
@gzliudan gzliudan changed the title fix(core/vm): simplify tracer hook invocation in interpreter loop #31074 fix(core/vm): trace before memory expansion #31074 Apr 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants