Closed
Description
Description
Some test executables fail with the "call stack exhausted" error.
What they have in common:
- they all have many test cases
- the error occurs only when building with the latest (swift-wasm-DEVELOPMENT-SNAPSHOT-2024-03-22-a) toolchain
- swift-wasm-DEVELOPMENT-SNAPSHOT-2024-03-20-a doesn't have this issue
Reproduction
- https://github.com/kkk669/wasm-test-example (almost minimal)
- ci: bump Swift SDK to swift-wasm-DEVELOPMENT-SNAPSHOT-2024-03-22-a kkebo/swift-syntax#18
- ❌ swift-wasm-DEVELOPMENT-SNAPSHOT-2024-03-22-a
- ✅ swift-wasm-DEVELOPMENT-SNAPSHOT-2024-03-20-a
Expected behavior
I expected the test executable to succeed in running.
In fact, the executable built with the previous (swift-wasm-DEVELOPMENT-SNAPSHOT-2024-03-20-a) toolchain has succeeded.
Environment
- Linux (x86_64, aarch64)
- Swift main snapshot (swift-DEVELOPMENT-SNAPSHOT-2024-03-20-a)
- Swift SDK (swift-wasm-DEVELOPMENT-SNAPSHOT-2024-03-22-a)
Metadata
Metadata
Assignees
Labels
No labels