Skip to content

scripts: runtime ABI checker, codegen calls vs runtime signatures (WASI phase 3a) #11398

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
proggeramlug merged 1 commit into from
Sep 26, 2026
Merged

scripts: runtime ABI checker, codegen calls vs runtime signatures (WASI phase 3a) #11398

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions .github/workflows/wasi-check.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,8 @@ on:
- "Cargo.lock"
- "rust-toolchain.toml"
- "scripts/wasi_check.sh"
- "scripts/runtime_abi_check.py"
- "crates/perry-codegen/src/**"
- ".github/workflows/wasi-check.yml"
# Main-line arm: one daily sweep, not one run per merge — see
# docs/src/testing/ci-gate-scheduling.md before adding `push: branches: [main]`.
Expand Down Expand Up @@ -68,3 +70,11 @@ jobs:

- name: perry-runtime builds for wasm32-wasip2
run: ./scripts/wasi_check.sh

# Report-only until #11378 turns the wasm32 categories into a ratchet:
# codegen's runtime declarations and call sites vs the runtime's real
# `extern "C"` signatures. The self-test proves every category can fire.
- name: Runtime ABI check (self-test)
run: python3 scripts/runtime_abi_check.py --self-test
- name: Runtime ABI check (report)
run: python3 scripts/runtime_abi_check.py
Loading
Loading