Hello,
After more investigation, I found that the first problem is due to non-English
characters in executable path.
As for the second one, toolchain version is GCC 6.1.0 (although I’m not sure
which exact commit because it’s a pre-built package) and the binary doesn’t
seem to contain RV64C
I've never seen that first error before, but none of the code in that
backtrace belongs to RISC-V. As for the second one, do you know which
version of the toolchain you're using? Without the patch Jason linked you
to, gem5 only supports this commit of riscv-tools
Hi Jason,
I'm not an expert on RISC-V, but this patch on gerrit may help:
https://gem5-review.googlesource.com/c/3860/.
Cheers,
Jason
On Wed, Jul 5, 2017 at 10:56 AM 孙靖渊 wrote:
> Hello,
> I’m trying to setup gem5 with RISC-V, the example hello binary in ./test
> folder
Hello,
I’m trying to setup gem5 with RISC-V, the example hello binary in ./test folder
works fine on both scenario but
A) On Ubuntu (both 17.04 and 14.04), whatever binary (compiled with
riscv64-unknown-elf-gcc) I supply, I would get the error:
> Traceback (most recent call last):
> File "",