Stream: git-wasmtime

Topic: wasmtime / issue #4006 x64: use `mov` instead of `movzx` ...

Wasmtime GitHub notifications bot (Apr 07 2022 at 23:56):

abrown opened issue #4006:

See https://github.com/bytecodealliance/wasmtime/pull/3993#discussion_r845374694.

Wasmtime GitHub notifications bot (Apr 08 2022 at 09:13):

akirilov-arm labeled issue #4006:

See https://github.com/bytecodealliance/wasmtime/pull/3993#discussion_r845374694.

Wasmtime GitHub notifications bot (Apr 08 2022 at 09:13):

akirilov-arm labeled issue #4006:

See https://github.com/bytecodealliance/wasmtime/pull/3993#discussion_r845374694.

Wasmtime GitHub notifications bot (Apr 12 2022 at 21:57):

abrown commented on issue #4006:

@cfallin, looking into this a bit more: were we using movzx here to avoid partial register stalls/dependencies?

Wasmtime GitHub notifications bot (Apr 12 2022 at 22:31):

cfallin commented on issue #4006:

@abrown that makes sense for 8 or 16-bit loads, I suppose. But for 32-bit loads, aren't the semantics such that mov eax, [mem] already zeroes the upper 32 bits, so there shouldn't be a partial-register stall?

Last updated: Dec 23 2024 at 12:05 UTC