Stream: git-wasmtime

Topic: wasmtime / issue #3053 assert failure on modern intel cpu...

view this post on Zulip Wasmtime GitHub notifications bot (Jul 02 2021 at 14:17):

programmerjake opened issue #3053:

See upstream: https://github.com/gz/rust-cpuid/issues/45#issuecomment-873001709
Running into this issue via wasmtime PyPI package used by yowasp-yosys.
See also: https://github.com/YoWASP/yosys/issues/22

view this post on Zulip Wasmtime GitHub notifications bot (Jul 02 2021 at 14:17):

programmerjake labeled issue #3053:

See upstream: https://github.com/gz/rust-cpuid/issues/45#issuecomment-873001709
Running into this issue via wasmtime PyPI package used by yowasp-yosys.
See also: https://github.com/YoWASP/yosys/issues/22

view this post on Zulip Wasmtime GitHub notifications bot (Jul 02 2021 at 14:34):

alexcrichton commented on issue #3053:

Thanks for the report! It looks like this is coming from the raw-cpuid crate which was removed in https://github.com/bytecodealliance/wasmtime/pull/2607. Looking at yosys I think an older version of Wasmtime is being pulled in, so I think that this isn't a bug in Wasmtime itself but perhaps a place where the python wasmtime dep needs to be updated?

view this post on Zulip Wasmtime GitHub notifications bot (Jul 03 2021 at 01:02):

programmerjake commented on issue #3053:

Ok, thanks!

view this post on Zulip Wasmtime GitHub notifications bot (Jul 03 2021 at 01:02):

programmerjake closed issue #3053:

See upstream: https://github.com/gz/rust-cpuid/issues/45#issuecomment-873001709
Running into this issue via wasmtime PyPI package used by yowasp-yosys.
See also: https://github.com/YoWASP/yosys/issues/22

Last updated: Nov 22 2024 at 16:03 UTC