afonso360 opened issue #5467:
:wave: Hey
.clif
Test Casetest interpret test run target aarch64 function %iabs_i128(i128) -> i128 { block0(v0: i128): v1 = iabs.i128 v0 return v1 } ; run: %iabs_i128(1) == 1 ; run: %iabs_i128(-1) == 1
Steps to Reproduce
clif-util test ./the-above.clif
Expected Results
The above test to pass
Actual Results
Finished dev [unoptimized + debuginfo] target(s) in 0.17s 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 #1' panicked at 'should be implemented in ISLE: inst = `v1 = iabs.i128 v0`, type = `Some(types::I128)`', cranelift/codegen/src/machinst/lower.rs:753:21 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ERROR cranelift_filetests::concurrent > FAIL: panicked in worker #1: should be implemented in ISLE: inst = `v1 = iabs.i128 v0`, type = `Some(types::I128)` FAIL ./lmao.clif: panicked in worker #1: should be implemented in ISLE: inst = `v1 = iabs.i128 v0`, type = `Some(types::I128)` 1 tests Error: 1 failure
Versions and Environment
Cranelift version or commit: main
Operating system: Linux
Architecture: AArch64
afonso360 labeled issue #5467:
:wave: Hey
.clif
Test Casetest interpret test run target aarch64 function %iabs_i128(i128) -> i128 { block0(v0: i128): v1 = iabs.i128 v0 return v1 } ; run: %iabs_i128(1) == 1 ; run: %iabs_i128(-1) == 1
Steps to Reproduce
clif-util test ./the-above.clif
Expected Results
The above test to pass
Actual Results
Finished dev [unoptimized + debuginfo] target(s) in 0.17s 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 #1' panicked at 'should be implemented in ISLE: inst = `v1 = iabs.i128 v0`, type = `Some(types::I128)`', cranelift/codegen/src/machinst/lower.rs:753:21 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ERROR cranelift_filetests::concurrent > FAIL: panicked in worker #1: should be implemented in ISLE: inst = `v1 = iabs.i128 v0`, type = `Some(types::I128)` FAIL ./lmao.clif: panicked in worker #1: should be implemented in ISLE: inst = `v1 = iabs.i128 v0`, type = `Some(types::I128)` 1 tests Error: 1 failure
Versions and Environment
Cranelift version or commit: main
Operating system: Linux
Architecture: AArch64
afonso360 labeled issue #5467:
:wave: Hey
.clif
Test Casetest interpret test run target aarch64 function %iabs_i128(i128) -> i128 { block0(v0: i128): v1 = iabs.i128 v0 return v1 } ; run: %iabs_i128(1) == 1 ; run: %iabs_i128(-1) == 1
Steps to Reproduce
clif-util test ./the-above.clif
Expected Results
The above test to pass
Actual Results
Finished dev [unoptimized + debuginfo] target(s) in 0.17s 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 #1' panicked at 'should be implemented in ISLE: inst = `v1 = iabs.i128 v0`, type = `Some(types::I128)`', cranelift/codegen/src/machinst/lower.rs:753:21 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ERROR cranelift_filetests::concurrent > FAIL: panicked in worker #1: should be implemented in ISLE: inst = `v1 = iabs.i128 v0`, type = `Some(types::I128)` FAIL ./lmao.clif: panicked in worker #1: should be implemented in ISLE: inst = `v1 = iabs.i128 v0`, type = `Some(types::I128)` 1 tests Error: 1 failure
Versions and Environment
Cranelift version or commit: main
Operating system: Linux
Architecture: AArch64
p3achyjr commented on issue #5467:
I can work on this--seems like a reasonable follow-up to https://github.com/bytecodealliance/wasmtime/issues/5466 :)
p3achyjr commented on issue #5467:
qq--how do we run aarch64 tests if we only have an x86 machine? I don't see qemu in my directory anywhere, even though it seems like that's how CI is being run.
afonso360 commented on issue #5467:
Have a look at the cross-compiling document It describes how we configure QEMU to run as part of
cargo test
andcargo run
. A super useful way of doing things!If you'd like to run the full testsuite we have a separate script that you can use:
./ci/run-tests.sh --target aarch64-unknown-linux-gnu --locked
p3achyjr commented on issue #5467:
Thanks for getting back! Super helpful. Everything passes :)
p3achyjr edited a comment on issue #5467:
Thanks for getting back! Really appreciate it. Everything passes :)
afonso360 commented on issue #5467:
This has been implemented in #7185. Thanks!
afonso360 closed issue #5467:
:wave: Hey
.clif
Test Casetest interpret test run target aarch64 function %iabs_i128(i128) -> i128 { block0(v0: i128): v1 = iabs.i128 v0 return v1 } ; run: %iabs_i128(1) == 1 ; run: %iabs_i128(-1) == 1
Steps to Reproduce
clif-util test ./the-above.clif
Expected Results
The above test to pass
Actual Results
Finished dev [unoptimized + debuginfo] target(s) in 0.17s 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 #1' panicked at 'should be implemented in ISLE: inst = `v1 = iabs.i128 v0`, type = `Some(types::I128)`', cranelift/codegen/src/machinst/lower.rs:753:21 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ERROR cranelift_filetests::concurrent > FAIL: panicked in worker #1: should be implemented in ISLE: inst = `v1 = iabs.i128 v0`, type = `Some(types::I128)` FAIL ./lmao.clif: panicked in worker #1: should be implemented in ISLE: inst = `v1 = iabs.i128 v0`, type = `Some(types::I128)` 1 tests Error: 1 failure
Versions and Environment
Cranelift version or commit: main
Operating system: Linux
Architecture: AArch64
Last updated: Dec 23 2024 at 13:07 UTC