wasmtime / issue #5453 Cranelift: `select_spectre_guard` ... · git-wasmtime

Stream: git-wasmtime

Topic: wasmtime / issue #5453 Cranelift: `select_spectre_guard` ...

Wasmtime GitHub notifications bot (Dec 16 2022 at 14:33):

afonso360 labeled issue #5453:

:wave: Hey,

Fuzzgen found this when adding support for this instruction. This is very similar to #5200 but with select_spectre_guard instead of select.

`.clif` Test Case

test interpret
test run
target aarch64

function %a(i128, i128, i128) -> i128 {
block0(v0: i128, v1: i128, v2: i128):
    v3 = select_spectre_guard.i128 v0, v1, v2
    return v3
}
; run: %a(1, 2, 3) == 2

Steps to Reproduce

clif-util test ./the-above.clif

Expected Results

The above tests to pass.

Actual Results

    Finished dev [unoptimized + debuginfo] target(s) in 0.15s
     Running `qemu-aarch64 -L /usr/aarch64-linux-gnu -E LD_LIBRARY_PATH=/usr/aarch64-linux-gnu/lib /home/afonso/git/wasmtime/target/aarch64-unknown-linux-gnu/debug/clif-util test ./lmao.clif`
thread 'worker #0' panicked at 'internal error: entered unreachable code: no rule matched for term put_in_reg_zext64 at src/isa/aarch64/inst.isle line 2807; should it be partial?', /home/afonso/git/wasmtime/target/aarch64-unknown-linux-gnu/debug/build/cranelift-codegen-85be69de44e3848b/out/isle_aarch64.rs:5567:12
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 ERROR cranelift_filetests::concurrent > FAIL: panicked in worker #0: internal error: entered unreachable code: no rule matched for term put_in_reg_zext64 at src/isa/aarch64/inst.isle line 2807; should it be partial?
FAIL ./lmao.clif: panicked in worker #0: internal error: entered unreachable code: no rule matched for term put_in_reg_zext64 at src/isa/aarch64/inst.isle line 2807; should it be partial?
1 tests
Error: 1 failure

Versions and Environment

Cranelift version or commit: main
Operating system: Linux
Architecture: AArch64

Extra Info

This is giving a slightly different error than the other one, but I think we are missing the proper lowering rule either way.

Wasmtime GitHub notifications bot (Dec 16 2022 at 14:33):

afonso360 labeled issue #5453:

:wave: Hey,

Fuzzgen found this when adding support for this instruction. This is very similar to #5200 but with select_spectre_guard instead of select.

`.clif` Test Case

test interpret
test run
target aarch64

function %a(i128, i128, i128) -> i128 {
block0(v0: i128, v1: i128, v2: i128):
    v3 = select_spectre_guard.i128 v0, v1, v2
    return v3
}
; run: %a(1, 2, 3) == 2

Steps to Reproduce

clif-util test ./the-above.clif

Expected Results

The above tests to pass.

Actual Results

    Finished dev [unoptimized + debuginfo] target(s) in 0.15s
     Running `qemu-aarch64 -L /usr/aarch64-linux-gnu -E LD_LIBRARY_PATH=/usr/aarch64-linux-gnu/lib /home/afonso/git/wasmtime/target/aarch64-unknown-linux-gnu/debug/clif-util test ./lmao.clif`
thread 'worker #0' panicked at 'internal error: entered unreachable code: no rule matched for term put_in_reg_zext64 at src/isa/aarch64/inst.isle line 2807; should it be partial?', /home/afonso/git/wasmtime/target/aarch64-unknown-linux-gnu/debug/build/cranelift-codegen-85be69de44e3848b/out/isle_aarch64.rs:5567:12
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 ERROR cranelift_filetests::concurrent > FAIL: panicked in worker #0: internal error: entered unreachable code: no rule matched for term put_in_reg_zext64 at src/isa/aarch64/inst.isle line 2807; should it be partial?
FAIL ./lmao.clif: panicked in worker #0: internal error: entered unreachable code: no rule matched for term put_in_reg_zext64 at src/isa/aarch64/inst.isle line 2807; should it be partial?
1 tests
Error: 1 failure

Versions and Environment

Cranelift version or commit: main
Operating system: Linux
Architecture: AArch64

Extra Info

This is giving a slightly different error than the other one, but I think we are missing the proper lowering rule either way.

Wasmtime GitHub notifications bot (Dec 16 2022 at 14:33):

afonso360 opened issue #5453:

:wave: Hey,

Fuzzgen found this when adding support for this instruction. This is very similar to #5200 but with select_spectre_guard instead of select.

`.clif` Test Case

test interpret
test run
target aarch64

function %a(i128, i128, i128) -> i128 {
block0(v0: i128, v1: i128, v2: i128):
    v3 = select_spectre_guard.i128 v0, v1, v2
    return v3
}
; run: %a(1, 2, 3) == 2

Steps to Reproduce

clif-util test ./the-above.clif

Expected Results

The above tests to pass.

Actual Results

    Finished dev [unoptimized + debuginfo] target(s) in 0.15s
     Running `qemu-aarch64 -L /usr/aarch64-linux-gnu -E LD_LIBRARY_PATH=/usr/aarch64-linux-gnu/lib /home/afonso/git/wasmtime/target/aarch64-unknown-linux-gnu/debug/clif-util test ./lmao.clif`
thread 'worker #0' panicked at 'internal error: entered unreachable code: no rule matched for term put_in_reg_zext64 at src/isa/aarch64/inst.isle line 2807; should it be partial?', /home/afonso/git/wasmtime/target/aarch64-unknown-linux-gnu/debug/build/cranelift-codegen-85be69de44e3848b/out/isle_aarch64.rs:5567:12
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 ERROR cranelift_filetests::concurrent > FAIL: panicked in worker #0: internal error: entered unreachable code: no rule matched for term put_in_reg_zext64 at src/isa/aarch64/inst.isle line 2807; should it be partial?
FAIL ./lmao.clif: panicked in worker #0: internal error: entered unreachable code: no rule matched for term put_in_reg_zext64 at src/isa/aarch64/inst.isle line 2807; should it be partial?
1 tests
Error: 1 failure

Versions and Environment

Cranelift version or commit: main
Operating system: Linux
Architecture: AArch64

Extra Info

This is giving a slightly different error than the other one, but I think we are missing the proper lowering rule either way.

Wasmtime GitHub notifications bot (Dec 16 2022 at 14:33):

afonso360 edited issue #5453:

:wave: Hey,

Fuzzgen found this when adding support for this instruction. This is very similar to #5200 but with select_spectre_guard instead of select.

`.clif` Test Case

test interpret
test run
target aarch64

function %a(i128, i128, i128) -> i128 {
block0(v0: i128, v1: i128, v2: i128):
    v3 = select_spectre_guard.i128 v0, v1, v2
    return v3
}
; run: %a(1, 2, 3) == 2

Steps to Reproduce

clif-util test ./the-above.clif

Expected Results

The above tests to pass.

Actual Results

    Finished dev [unoptimized + debuginfo] target(s) in 0.15s
     Running `qemu-aarch64 -L /usr/aarch64-linux-gnu -E LD_LIBRARY_PATH=/usr/aarch64-linux-gnu/lib /home/afonso/git/wasmtime/target/aarch64-unknown-linux-gnu/debug/clif-util test ./lmao.clif`
thread 'worker #0' panicked at 'internal error: entered unreachable code: no rule matched for term put_in_reg_zext64 at src/isa/aarch64/inst.isle line 2807; should it be partial?', /home/afonso/git/wasmtime/target/aarch64-unknown-linux-gnu/debug/build/cranelift-codegen-85be69de44e3848b/out/isle_aarch64.rs:5567:12
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 ERROR cranelift_filetests::concurrent > FAIL: panicked in worker #0: internal error: entered unreachable code: no rule matched for term put_in_reg_zext64 at src/isa/aarch64/inst.isle line 2807; should it be partial?
FAIL ./lmao.clif: panicked in worker #0: internal error: entered unreachable code: no rule matched for term put_in_reg_zext64 at src/isa/aarch64/inst.isle line 2807; should it be partial?
1 tests
Error: 1 failure

Versions and Environment

Cranelift version or commit: main
Operating system: Linux
Architecture: AArch64

Extra Info

This is giving a slightly different error than the other one, but I think we are missing the proper lowering rule either way.

Wasmtime GitHub notifications bot (Dec 16 2022 at 22:18):

cfallin closed issue #5453:

:wave: Hey,

Fuzzgen found this when adding support for this instruction. This is very similar to #5200 but with select_spectre_guard instead of select.

`.clif` Test Case

test interpret
test run
target aarch64

function %a(i128, i128, i128) -> i128 {
block0(v0: i128, v1: i128, v2: i128):
    v3 = select_spectre_guard.i128 v0, v1, v2
    return v3
}
; run: %a(1, 2, 3) == 2

Steps to Reproduce

clif-util test ./the-above.clif

Expected Results

The above tests to pass.

Actual Results

    Finished dev [unoptimized + debuginfo] target(s) in 0.15s
     Running `qemu-aarch64 -L /usr/aarch64-linux-gnu -E LD_LIBRARY_PATH=/usr/aarch64-linux-gnu/lib /home/afonso/git/wasmtime/target/aarch64-unknown-linux-gnu/debug/clif-util test ./lmao.clif`
thread 'worker #0' panicked at 'internal error: entered unreachable code: no rule matched for term put_in_reg_zext64 at src/isa/aarch64/inst.isle line 2807; should it be partial?', /home/afonso/git/wasmtime/target/aarch64-unknown-linux-gnu/debug/build/cranelift-codegen-85be69de44e3848b/out/isle_aarch64.rs:5567:12
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 ERROR cranelift_filetests::concurrent > FAIL: panicked in worker #0: internal error: entered unreachable code: no rule matched for term put_in_reg_zext64 at src/isa/aarch64/inst.isle line 2807; should it be partial?
FAIL ./lmao.clif: panicked in worker #0: internal error: entered unreachable code: no rule matched for term put_in_reg_zext64 at src/isa/aarch64/inst.isle line 2807; should it be partial?
1 tests
Error: 1 failure

Versions and Environment

Cranelift version or commit: main
Operating system: Linux
Architecture: AArch64

Extra Info

This is giving a slightly different error than the other one, but I think we are missing the proper lowering rule either way.

Last updated: Nov 22 2024 at 17:03 UTC

Stream: git-wasmtime

Topic: wasmtime / issue #5453 Cranelift: `select_spectre_guard` ...

Wasmtime GitHub notifications bot (Dec 16 2022 at 14:33):

.clif Test Case

Steps to Reproduce

Expected Results

Actual Results

Versions and Environment

Extra Info

Wasmtime GitHub notifications bot (Dec 16 2022 at 14:33):

.clif Test Case

Steps to Reproduce

Expected Results

Actual Results

Versions and Environment

Extra Info

Wasmtime GitHub notifications bot (Dec 16 2022 at 14:33):

.clif Test Case

Steps to Reproduce

Expected Results

Actual Results

Versions and Environment

Extra Info

Wasmtime GitHub notifications bot (Dec 16 2022 at 14:33):

.clif Test Case

Steps to Reproduce

Expected Results

Actual Results

Versions and Environment

Extra Info

Wasmtime GitHub notifications bot (Dec 16 2022 at 22:18):

.clif Test Case

Steps to Reproduce

Expected Results

Actual Results

Versions and Environment

Extra Info

`.clif` Test Case

`.clif` Test Case

`.clif` Test Case

`.clif` Test Case

`.clif` Test Case