Stream: git-wasmtime

Topic: wasmtime / issue #3304 Implement `vany_true` and `vall_tr...

view this post on Zulip Wasmtime GitHub notifications bot (Sep 06 2021 at 10:16):

afonso360 commented on issue #3304:

The aarch64 CI failure is interesting. It does not happen locally for me and I'm using a older version than CI.

Locally:

$ qemu-aarch64 --version
qemu-aarch64 version 4.2.1 (Debian 1:4.2-3ubuntu6.16)
Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers

CI I think is using a custom build, but shows up as 6.0.0:

  shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
  env:
    QEMU_BUILD_VERSION: 6.0.0

view this post on Zulip Wasmtime GitHub notifications bot (Sep 06 2021 at 10:19):

afonso360 edited a comment on issue #3304:

The aarch64 CI failure is interesting. It does not happen locally for me and I'm using a older version than CI.

Locally:

$ qemu-aarch64 --version
qemu-aarch64 version 4.2.1 (Debian 1:4.2-3ubuntu6.16)
Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers

CI I think is using a custom build, but shows up as 6.0.0:

  shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
  env:
    QEMU_BUILD_VERSION: 6.0.0

view this post on Zulip Wasmtime GitHub notifications bot (Sep 06 2021 at 10:20):

afonso360 edited a comment on issue #3304:

The aarch64 CI failure is interesting. It does not happen locally for me and I'm using a older version than CI.

Locally:

$ qemu-aarch64 --version
qemu-aarch64 version 4.2.1 (Debian 1:4.2-3ubuntu6.16)

CI I think is using a custom build, but shows up as 6.0.0:

  shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
  env:
    QEMU_BUILD_VERSION: 6.0.0

view this post on Zulip Wasmtime GitHub notifications bot (Sep 06 2021 at 10:22):

afonso360 edited a comment on issue #3304:

The aarch64 CI failure is interesting. It does not happen locally for me and I'm using an older version than CI.

Locally:

$ qemu-aarch64 --version
qemu-aarch64 version 4.2.1 (Debian 1:4.2-3ubuntu6.16)

CI I think is using a custom build, but shows up as 6.0.0:

  shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
  env:
    QEMU_BUILD_VERSION: 6.0.0

view this post on Zulip Wasmtime GitHub notifications bot (Sep 06 2021 at 11:09):

afonso360 edited a comment on issue #3304:

The aarch64 CI failure is interesting. It does not happen locally for me and I'm using an older version than CI.

Locally:

$ qemu-aarch64 --version
qemu-aarch64 version 4.2.1 (Debian 1:4.2-3ubuntu6.16)

CI I think is using a custom build, but shows up as 6.0.0:

  shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
  env:
    QEMU_BUILD_VERSION: 6.0.0

Edit: Compiled qemu 6.0.0 and 6.1.0 as described in the CI script, and they both fail with illegal instruction.

Reduced testcase:

function %vany_true_b64x2() -> b1 {
block0:
    v0 = vconst.b64x2 [false false]
    v1 = vany_true v0
    return v1
}
; run: %vany_true_b64x2() == false

This is the only instruction that fails

view this post on Zulip Wasmtime GitHub notifications bot (Sep 06 2021 at 11:19):

afonso360 edited a comment on issue #3304:

The aarch64 CI failure is interesting. It does not happen locally for me and I'm using an older version than CI.

Locally:

$ qemu-aarch64 --version
qemu-aarch64 version 4.2.1 (Debian 1:4.2-3ubuntu6.16)

CI I think is using a custom build, but shows up as 6.0.0:

  shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
  env:
    QEMU_BUILD_VERSION: 6.0.0

Edit: Compiled qemu 6.0.0 and 6.1.0 as described in the CI script, and they both fail with illegal instruction.

Reduced testcase:

function %vany_true_b64x2() -> b1 {
block0:
    v0 = vconst.b64x2 [false false]
    v1 = vany_true v0
    return v1
}
; run: %vany_true_b64x2() == false

This is the only instruction that fails.

I think I got something wrong along the way, it looks simd-vanytrue.clif always fails, even in my local qemu :face_palm:

view this post on Zulip Wasmtime GitHub notifications bot (Sep 06 2021 at 11:26):

afonso360 edited a comment on issue #3304:

The aarch64 CI failure is interesting. It does not happen locally for me and I'm using an older version than CI.

Locally:

$ qemu-aarch64 --version
qemu-aarch64 version 4.2.1 (Debian 1:4.2-3ubuntu6.16)

CI I think is using a custom build, but shows up as 6.0.0:

  shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
  env:
    QEMU_BUILD_VERSION: 6.0.0

Edit: Compiled qemu 6.0.0 and 6.1.0 as described in the CI script, and they both fail with illegal instruction.

Reduced testcase:

function %vany_true_b64x2() -> b1 {
block0:
    v0 = vconst.b64x2 [false false]
    v1 = vany_true v0
    return v1
}
; run: %vany_true_b64x2() == false

This is the only instruction that fails.

Edit2: I think I got something wrong along the way, it looks simd-vanytrue.clif always fails, even in my local qemu :face_palm:

view this post on Zulip Wasmtime GitHub notifications bot (Sep 07 2021 at 08:12):

afonso360 edited a comment on issue #3304:

The aarch64 CI failure is interesting. It does not happen locally for me and I'm using an older version than CI.

Locally:

$ qemu-aarch64 --version
qemu-aarch64 version 4.2.1 (Debian 1:4.2-3ubuntu6.16)

CI I think is using a custom build, but shows up as 6.0.0:

  shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
  env:
    QEMU_BUILD_VERSION: 6.0.0

Edit: Compiled qemu 6.0.0 and 6.1.0 as described in the CI script, and they both fail with illegal instruction.

Reduced testcase:

function %vany_true_b64x2() -> b1 {
block0:
    v0 = vconst.b64x2 [false false]
    v1 = vany_true v0
    return v1
}
; run: %vany_true_b64x2() == false

This is the only instruction that fails.

Edit2: I think I got something wrong along the way, it looks simd-vanytrue.clif always fails, even in my local qemu :face_palm:

Last updated: Dec 06 2025 at 06:05 UTC