Skip to content

Conversation

@alexreinking
Copy link
Member

This GEP was not in fact guaranteed to be in-bounds. This was discovered by a failure in the WASM version of correctness_indexing_access_undef after a change to LLVM's LICM declined to hoist part of the computation.

LLVM reference: llvm/llvm-project#151492

Drive-by cleanup in test/generator/CMakeLists.txt.

Fixes #8766

This GEP was not in fact guaranteed to be in-bounds. This was discovered by a failure in the WASM version of correctness_indexing_access_undef after a change to LLVM's LICM declined to hoist part of the computation.

LLVM reference: llvm/llvm-project#151492
@alexreinking
Copy link
Member Author

alexreinking commented Aug 20, 2025

This seems to have introduced some new failures. That or LLVM main did.

@abadams
Copy link
Member

abadams commented Aug 20, 2025

Looks like it broke one of the vector load tests in simd_op_check_wasm for all tested versions of llvm.

@abadams abadams merged commit 3e1e028 into main Aug 27, 2025
11 of 19 checks passed
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.

Failing test: correctness_indexing_access_undef

3 participants