Skip to content

Fix Memory64Lowering table.copy size wrapping for mixed tables #8319

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kripken merged 1 commit into from
Feb 13, 2026
+69 −1
Merged

Fix Memory64Lowering table.copy size wrapping for mixed tables #8319

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion src/passes/Memory64Lowering.cpp
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -237,7 +237,12 @@ struct Memory64Lowering : public WalkerPass<PostWalker<Memory64Lowering>> {
void visitTableCopy(TableCopy* curr) {
wrapTableAddress64(curr->dest, curr->destTable);
wrapTableAddress64(curr->source, curr->sourceTable);
wrapTableAddress64(curr->size, curr->destTable);
// The size type is i64 only when both tables are 64-bit.
auto& module = *getModule();
if (module.getTable(curr->destTable)->is64() &&
module.getTable(curr->sourceTable)->is64()) {
wrapAddress64(curr->size, curr->destTable, true);
}
}

void visitTableInit(TableInit* curr) {
Expand Down
63 changes: 63 additions & 0 deletions test/lit/passes/memory64-lowering-table-copy.wast
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,63 @@
;; NOTE: Assertions have been generated by update_lit_checks.py --all-items and should not be edited.

;; RUN: foreach %s %t wasm-opt --memory64-lowering --enable-memory64 --enable-reference-types --enable-bulk-memory -S -o - | filecheck %s

;; Test that table.copy with mixed 32/64-bit tables correctly handles the
;; size operand type.
(module
;; CHECK: (type $0 (func))

;; CHECK: (table $t64 10 funcref)
(table $t64 i64 10 funcref)
;; CHECK: (table $t32 10 funcref)
(table $t32 10 funcref)

;; CHECK: (func $table-copy-mixed-64-to-32
;; CHECK-NEXT: (table.copy $t32 $t64
;; CHECK-NEXT: (i32.const 0)
;; CHECK-NEXT: (i32.wrap_i64
;; CHECK-NEXT: (i64.const 0)
;; CHECK-NEXT: )
;; CHECK-NEXT: (i32.const 5)
;; CHECK-NEXT: )
;; CHECK-NEXT: )
(func $table-copy-mixed-64-to-32
;; Copy from 64-bit table to 32-bit table. The size is i32 because not
;; both tables are 64-bit, so no wrapping of size should occur.
(table.copy $t32 $t64 (i32.const 0) (i64.const 0) (i32.const 5))
)

;; CHECK: (func $table-copy-mixed-32-to-64
;; CHECK-NEXT: (table.copy $t64 $t32
;; CHECK-NEXT: (i32.wrap_i64
;; CHECK-NEXT: (i64.const 0)
;; CHECK-NEXT: )
;; CHECK-NEXT: (i32.const 0)
;; CHECK-NEXT: (i32.const 5)
;; CHECK-NEXT: )
;; CHECK-NEXT: )
(func $table-copy-mixed-32-to-64
;; Copy from 32-bit table to 64-bit table. The size is i32 because not
;; both tables are 64-bit, so no wrapping of size should occur.
(table.copy $t64 $t32 (i64.const 0) (i32.const 0) (i32.const 5))
)

;; CHECK: (func $table-copy-both-64
;; CHECK-NEXT: (table.copy $t64 $t64
;; CHECK-NEXT: (i32.wrap_i64
;; CHECK-NEXT: (i64.const 0)
;; CHECK-NEXT: )
;; CHECK-NEXT: (i32.wrap_i64
;; CHECK-NEXT: (i64.const 5)
;; CHECK-NEXT: )
;; CHECK-NEXT: (i32.wrap_i64
;; CHECK-NEXT: (i64.const 3)
;; CHECK-NEXT: )
;; CHECK-NEXT: )
;; CHECK-NEXT: )
(func $table-copy-both-64
;; Copy between same 64-bit table. All operands including size are i64
;; and should be wrapped.
(table.copy $t64 $t64 (i64.const 0) (i64.const 5) (i64.const 3))
)
)
Loading