Hi Philippe, let me resend the table as it was corrupted in the last mail.
A: !defined(CONFIG_TCG_INTERPRETER)
B: !defined(EMSCRIPTEN)
| A | B | && | || |
--+---+---+++
non-emcc + TCI| F | T | F | T |
non-emcc + non-TCI| T | T | T | T |
emcc + TCI
Hi Philippe, thank you for the feedback.
> > diff --git a/tcg/tcg.c b/tcg/tcg.c
> > index dfd48b8264..154a4dafa7 100644
> > --- a/tcg/tcg.c
> > +++ b/tcg/tcg.c
> > @@ -136,6 +136,10 @@ static void tcg_out_goto_tb(TCGContext *s, int
which);
> > static void tcg_out_op(TCGContext *s, TCGOpcode opc,
Hi Kohei,
On 7/4/25 16:45, Kohei Tokunaga wrote:
A TB consists of a wasmTBHeader followed by the data listed below. The
wasmTBHeader contains pointers for each element:
- TCI code
- Wasm code
- Array of function indices imported into the Wasm instance
- Counter tracking the number of TB executi
> Eh TBH this is too much to review as a single patch.
>
> Do you already have an idea how different the wasm64 implementation can
be?
Sorry for the large patch. I'll split it into smaller patches in the next
version of the series.
With wasm64, instructions that manipulate pointers (e.g., ld/st,
On 7/4/25 16:45, Kohei Tokunaga wrote:
A TB consists of a wasmTBHeader followed by the data listed below. The
wasmTBHeader contains pointers for each element:
- TCI code
- Wasm code
- Array of function indices imported into the Wasm instance
- Counter tracking the number of TB executions
- Point
