Tanishqgithub

@grigohas No i haven't The authors have to give some idea regarding this

As you said if i use the gcc13.1.0 baremetal to run the benchmark.sh to setup the RISCV variables i don't have **/bin/riscv64-unknown- ; /bin/riscv64-unknown-gcc** to setup for RISCV_PREFIX ; RISCV_GCC...

I followed the commands in https://github.com/openhwgroup/cva6/blob/master/verif/README.md the commands i gave is : ``` 1. git clone --recursive https://github.com/riscv-collab/riscv-gnu-toolchain ~/Desktop/CVA6/cva6/riscv-gnu-toolchain 2. cd riscv-gnu-toolchain 3. git clone https://github.com/gcc-mirror/gcc -b releases/gcc-13 gcc-13 4....

@valentinThomazic Respected sir U understood my issue correctly, thanks for that I will check it out and let you know

@valentinThomazic Respected Sir I did try to run the ``` benchmark.sh ``` script after installing the ``` gcc 13.1.0 baremetal ``` as per main README 1. I ran the smoke...

Anyone please update on this issue

1. For ``` benchmark.sh ``` : I though similar to ```smoke_test.sh``` i could run this ``` benchmark.sh ``` as some testing file so i gave ```DV_SIMULATORS=veri-testharness,spike ``` If only ```...

1. Note the prerequists command i ran which is there in [1. ] in previous message is : ``` sudo apt update sudo apt-get install -y build-essential git doxygen python3-pip...

As per your suggestion i tried out to re-install verilator using the command ``` make -B verilator ``` after cleaning the path VERILATOR_ROOT I got this log file : [verilator.txt](https://github.com/user-attachments/files/16032422/verilator.txt)...

1. when i run ``` echo VERILATOR_ROOT ``` i got the following output :  2. the config.log file is attached here : [config.log](https://github.com/user-attachments/files/16038788/config.log)