The fesvr always looks for pk in riscv64-unknown-elf/bin - however, for a 32-bit pk it is in riscv32-unknown-elf/bin. This commit defines TARGET_ARCH (used in fesvr/htif.cc) based on the value of the --target flag if it is provided to configure. This makes it a bit easier to use Spike / fesvr/ pk for riscv32, as there doesn't seem to be any other straightforward way of telling fesvr where to look for pk.
I've tested this with toolchain builds for both riscv32-unknown-elf and riscv64-unknown-elf, and haven't come across any issues with it.
The fesvr always looks for
pk
inriscv64-unknown-elf/bin
- however, for a 32-bitpk
it is inriscv32-unknown-elf/bin
. This commit definesTARGET_ARCH
(used infesvr/htif.cc
) based on the value of the--target
flag if it is provided toconfigure
. This makes it a bit easier to use Spike / fesvr/ pk for riscv32, as there doesn't seem to be any other straightforward way of telling fesvr where to look forpk
.I've tested this with toolchain builds for both
riscv32-unknown-elf
andriscv64-unknown-elf
, and haven't come across any issues with it.