Skip to content

Update constant-table emission test for exact index checks - #865

Merged
ctate merged 2 commits into
mainfrom
ctate/update-constant-table-dd172e
Oct 11, 2026
Merged

ctate merged 2 commits into
mainfrom
ctate/update-constant-table-dd172e

Conversation

@ctate

@ctate ctate commented Oct 11, 2026

Copy link
Copy Markdown
Collaborator
  • Assert the signed round-trip index check the constant-table getter now emits
  • Fixes the test (san, 8/10) failure on main

@vercel

vercel Bot commented Oct 11, 2026 •

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
scriptc Ready Ready Preview, v0 Oct 11, 2026 7:48pm UTC

@ctate
ctate merged commit 9763428 into main Oct 11, 2026
52 checks passed
@ctate
ctate deleted the ctate/update-constant-table-dd172e branch October 11, 2026 19:52
cramforce added a commit that referenced this pull request Oct 11, 2026
f3cfa80 asserted that the canonical byte loop contains no `fptosi double`
at all, meaning no exact-index round trip. The fixture also coerces its
running sum with ToUint32, whose inline fast path legitimately uses
`fptosi double ... to i64`, so the test fails on main (aaccbb3) as well;
#865 merged before the shards that run it. Assert instead that no
`bytes.index` check block is emitted, which keeps the original intent
(no unproven-index path for a proven in-bounds induction index).

This branch was successfully deployed

1 active deployment
Preview — f3cfa80a Deployed Oct 11, 2026 by vercel[bot]
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