From aec27be648ccd55a529d8d75dbe8bca543ae959d Mon Sep 17 00:00:00 2001 From: Bruce Lai Date: Wed, 19 Apr 2023 00:30:57 -0700 Subject: [PATCH] Remove out-of-date description for testing RVV on QEMU Aafter commit in CL: https://chromium-review.googlesource.com/c/libyuv/libyuv/+/4429570 We don't need to hack the code for testing RVV on QEMU at all. Change-Id: Ic123d88b7ccc8dd54768e33cb0db363472be6ffc Signed-off-by: Bruce Lai Reviewed-on: https://chromium-review.googlesource.com/c/libyuv/libyuv/+/4442914 Reviewed-by: Frank Barchard Commit-Queue: Frank Barchard --- docs/getting_started.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/docs/getting_started.md b/docs/getting_started.md index ff1c185ad..37ffc7478 100644 --- a/docs/getting_started.md +++ b/docs/getting_started.md @@ -241,10 +241,6 @@ After running script, clang & qemu are built in `build-toolchain-qemu/riscv-clan ### Run on QEMU -To test RVV on user mode QEMU, we need to hack `source/cpu_id.cc`. By forcing `RiscvCpuCaps` to read from a dummy cpuinfo file instead of the host `/proc/cpuinfo`. Because the program detects CPU Caps from `/proc/cpuinfo` and determines whether to use RVV originally. - - sed -i 's+RiscvCpuCaps("/proc/cpuinfo+RiscvCpuCaps("../../unit_test/testdata/riscv64_rvv.txt+g' source/cpu_id.cc - #### Run libyuv_unittest on QEMU cd out/Release/ USE_RVV=ON \