coffee/libyuv
1
0
Fork 0
mirror of https://chromium.googlesource.com/libyuv/libyuv synced 2025-12-06 16:56:55 +08:00
Code Issues Packages Projects Releases Wiki Activity

Remove out-of-date description for testing RVV on QEMU

Browse Source 
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 <bruce.lai@sifive.com>
Reviewed-on: https://chromium-review.googlesource.com/c/libyuv/libyuv/+/4442914
Reviewed-by: Frank Barchard <fbarchard@chromium.org>
Commit-Queue: Frank Barchard <fbarchard@chromium.org>
This commit is contained in:
Bruce Lai 2023-04-19 00:30:57 -07:00 committed by libyuv LUCI CQ
parent c994782086
commit aec27be648
1 changed files with 0 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/getting_started.md
View File

@ -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 \