You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to commit 72dd5d7 but on a wasm
module level instead of inside a wasm function.
This is a conservative workaround to ensure that we don't lose any
chances of emitting operations that previously used static ILTypes but
will depend on a signature input for the migration to wasm-gc.
Bug: 448860865
Change-Id: Ife60126cabb8c49a0493736603611b9b2dd3e67b
Reviewed-on: https://chrome-internal-review.googlesource.com/c/v8/fuzzilli/+/8938986
Reviewed-by: Doga Yüksel <dyuksel@google.com>
Commit-Queue: Matthias Liedtke <mliedtke@google.com>
Copy file name to clipboardExpand all lines: Sources/Fuzzilli/Lifting/WasmLifter.swift
+8-1Lines changed: 8 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1224,7 +1224,12 @@ public class WasmLifter {
1224
1224
}
1225
1225
}
1226
1226
1227
-
/// This function updates the internal state of the lifter before actually emitting code to the wasm module. This should be invoked before we try to get the corresponding bytes for the Instruction
1227
+
/// This function updates the internal state of the lifter before actually emitting code to the
1228
+
/// wasm module. This should be invoked before we try to get the corresponding bytes for the
1229
+
/// Instruction.
1230
+
/// Returns true if the instruction requires emitting code into the module's code section (which
1231
+
/// means it is true for almost all instructions appearing inside a wasm function and false for
1232
+
/// all instructions outside of a wasm function like a Wasm memory definition).
0 commit comments