Skip to content

Use the configured size type for sequence arguments - #276

Open
zakariyaghazzol wants to merge 2 commits into
fprime-community:develfrom
zakariyaghazzol:fpy-seq-args-size-type
Open

zakariyaghazzol wants to merge 2 commits into
fprime-community:develfrom
zakariyaghazzol:fpy-seq-args-size-type

Conversation

@zakariyaghazzol

Copy link
Copy Markdown

Fixes #223.

Adopt the dictionary's unsigned SeqArgs size field and validate its capacity. Restore the layout and constructor defaults when switching cached dictionaries, and reset U64 when SeqArgs is absent.

Add 22 regressions for byte layouts, defaults, cache switching and sequence-call boundaries.

Testing: 1,684 passed with one existing XPASS; related suite 112 passed. Both real C++ harnesses rebuilt/probed as 32-bit and 64-bit executables with matching dictionaries; empty, constant, variable and full-capacity child calls pass with independently checked command bytes. The original compiler rejects the same U32 dictionaries. Black and diff checks pass.

No runtime, submodule, dependency or workflow changes included. The existing supplied Wasm harness compatibility patch was used locally.

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.

1 participant