WebAssembly / WebAssembly/binaryen

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

Open
#9,006 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
WebAssembly
Stars
8.6k
Forks
885
Avg merge
1d 19h
Merged PRs (30d)
69

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

--

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

Contributor guide

Open the contributing guide

First steps

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

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.

Assessment

Tech stack
wasm
Domain
compilers
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.