ctor-eval/flatten_overflow.wast lit test fails on x86 32-bit

Open

#9,006 opened on Aug 15, 2026 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 52/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Quiet
Tech stack: wasm
Domain: compilers

Research direction

Start by running the Binaryen lit test test/lit/ctor-eval/flatten_overflow.wast with wasm-ctor-eval on an x86 32-bit build, using the command shown in the report. Trace the exit code -11 and identify the cause of the crash; done means this test completes successfully on x86 32-bit without failing.

Written by the indexing model from the issue text.

Description

When running binaryen 132 test suite on x86 32-bit, I'm getting the following failure:

FAIL: Binaryen lit tests :: ctor-eval/flatten_overflow.wast (1 of 962)
******************** TEST 'Binaryen lit tests :: ctor-eval/flatten_overflow.wast' FAILED ********************
Exit Code: -11

Command Output (stdout):
--
# RUN: at line 6
/builddir/build/BUILD/binaryen-132-build/binaryen-version_132/redhat-linux-build/bin/wasm-ctor-eval /builddir/build/BUILD/binaryen-132-build/binaryen-version_132/test/lit/ctor-eval/flatten_overflow.wast --ctors=test --kept-exports=test --quiet -all
# executed command: /builddir/build/BUILD/binaryen-132-build/binaryen-version_132/redhat-linux-build/bin/wasm-ctor-eval /builddir/build/BUILD/binaryen-132-build/binaryen-version_132/test/lit/ctor-eval/flatten_overflow.wast --ctors=test --kept-exports=test --quiet -all
# note: command had no output on stdout or stderr
# error: command failed with exit status: -11

--

********************

Dominant language: WebAssembly
Stars: 8.6k
Forks: 885
Avg merge: 2d 1h
Merged PRs (30d): 70

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

`EoCodec` stores a `float` as a `double`, so a signaling-NaN float constant comes back with different bits Open

bug

Difficulty 2/5 1-3 hours Newbie friendliness 86/100

objectionary/jeo-maven-plugin#1774 · Opened Sep 21, 2026
cmd/compile/internal/syntax: printer panics on empty var () declaration statement Open

compiler/runtime

Difficulty 2/5 1-3 hours Newbie friendliness 76/100

golang/go#81633 · Opened Sep 21, 2026
[fx] Generated code for `operator.pow(-2, x)` is `-2 ** x`, which Python evaluates as `-(2 ** x)`: `GraphModule.forward` returns the wrong sign (`Interpreter` is correct); reachable from `torch.compile(dynamic=True)` via `(-1) ** x.shape[0]` Open

bot-triaged module: correctness (silent) module: fx release triage triage review

Difficulty 2/5 1-3 hours Newbie friendliness 86/100

pytorch/pytorch#197894 · 1 comment · Opened Sep 21, 2026
Grammar Gap: activated › effect clause › {self} deals damage equal to its power to target creature Open

area:mechanics ready-for-agent

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

fil-donadoni/tolaria#4317 · Opened Sep 21, 2026
`as-fixed.eo` keeps a minus sign on an all-zero result once `places` exceeds 15 Open

Difficulty 2/5 1-3 hours Newbie friendliness 82/100

objectionary/eo#8869 · 1 comment · Opened Sep 21, 2026

More Compilers issues