Skip to content

Keep CompoundSpan off splice opcodes (depends on #4740 and neo-vm#592) - #4742

Closed
cschuchardt88 wants to merge 6 commits into
neo-project:master-n3from
cschuchardt88:feature/compound-span
Closed

cschuchardt88 wants to merge 6 commits into
neo-project:master-n3from
cschuchardt88:feature/compound-span

Conversation

@cschuchardt88

@cschuchardt88 cschuchardt88 commented Aug 28, 2026 •

Copy link
Copy Markdown
Member

Description

Companion to neo-project/neo-vm#594 (depends on #4740 and neo-vm#592).

Related: neo-project/proposals#235 (compound binary / CAT on compounds).

ApplicationEngine.LimitsFor does not map VmFeatures.CompoundSpan from a hardfork. CAT / SUBSTR / LEFT / RIGHT / MEMCPY of Map/Array/Struct still FAULT. Host GetSafeSpan / AsSpan stay available without changing opcode behavior.

Change Log

  • Document CompoundSpan as host-only on LimitsFor
  • Tests: LimitsFor after Gorgon still omits the flag; CAT of empty Map FAULTS

Fixes # (issue)

Type of change

  • Optimization (the change is only an optimization)
  • Style (the change is only a code style for better maintenance or standard purpose)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

  • Unit Testing
  • Run Application
  • Local Computer Tests
  • No Testing

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

Status

Draft. CI cannot compile VmFeatures until neo-vm#592/#594 are in a published Neo.VM package. Includes #4740 commits until that lands.

ApplicationEngine.LimitsFor sets SafeSubStr (Echidna) and
StrictContainerAccess/BoundedShift (Gorgon). SUBSTR/SHL/SHR/HASKEY
overlays are removed; PICKITEM/SETITEM/REMOVE stay pre-Gorgon until
those land in neo-vm.

Uses a sibling ProjectReference to the neo-vm fork until a Neo.VM
package with VmFeatures is published.
CI and the upstream repo cannot use a sibling ProjectReference to
a local neo-vm checkout.
HF_Echidna enables SafeSubStr; HF_Gorgon enables StrictContainerAccess
and BoundedShift. LimitsFor starts from None so pre-fork heights keep
the old opcode paths.
Companion to neo-vm#594. LimitsFor does not set CompoundSpan, so
CAT/SUBSTR of Map/Array/Struct still FAULT. Host GetSafeSpan/AsSpan
stay available without changing opcode behavior.
@github-actions github-actions Bot added the N3 label Aug 28, 2026
Match neo-vm: the engine always passes the RET-coalesced instruction,
so diagnostics do not need a null check.
@cschuchardt88 cschuchardt88 changed the title Keep CompoundSpan off splice opcodes Keep CompoundSpan off splice opcodes (depends on #4740 and neo-vm#592) Aug 28, 2026
@cschuchardt88 cschuchardt88 mentioned this pull request Aug 28, 2026
3 of 11 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant