riscv-isa-sim/ci-tests/test-spike

#!/bin/bash
set -e

ROOT=`git rev-parse --show-toplevel`
NPROCS="$(nproc 2> /dev/null || sysctl -n hw.ncpu)"
HERE=`pwd`
CI="$( cd "$( dirname "${BASH_SOURCE[0]}" )" >/dev/null 2>&1 && pwd )"
INSTALL=$HERE/install
BUILD=$HERE/build
RUN=$HERE/run

# build pk
rm -rf $BUILD/pk
mkdir $BUILD/pk
cd $BUILD/pk
git clone https://github.com/riscv-software-src/riscv-pk.git
riscv-pk/configure --host=riscv64-linux-gnu --prefix=$INSTALL
make -j$NPROCS
make install

# build tests
rm -rf $RUN
mkdir -p $RUN
cd $RUN
riscv64-linux-gnu-gcc -static -O2 -o hello $CI/hello.c
riscv64-linux-gnu-gcc -static -O2 -o dummy-slliuw $CI/dummy-slliuw.c
riscv64-linux-gnu-gcc -static -O2 -o customcsr $CI/customcsr.c
riscv64-linux-gnu-gcc -static -O2 -o atomics $CI/atomics.c
riscv64-linux-gnu-gcc -static -O2 -march=rv64gcv -o vector-sum $CI/vector-sum.c

# run snippy-based tests
wget https://github.com/syntacore/snippy/releases/download/snippy-2.1/snippy-x86_64-linux.tar.xz
tar xf snippy-x86_64-linux.tar.xz

# test that snippy runs
bin/llvm-snippy --version | grep "Snippy version: 2.1.0"
PATH="$PATH:$RUN/bin" "$ROOT"/ci-tests/run-snippy-tests.sh "$RUN" "$ROOT"/ci-tests/snippy-tests "$INSTALL"/bin/spike

# check that including sim.h in an external project works
g++ -std=c++2a -I$INSTALL/include -L$INSTALL/lib $CI/testlib.cc -lriscv -o test-libriscv
g++ -std=c++2a -I$INSTALL/include -L$INSTALL/lib $CI/test-customext.cc -lriscv -o test-customext
g++ -std=c++2a -I$INSTALL/include -L$INSTALL/lib $CI/custom-csr.cc -lriscv -o test-custom-csr

# check that all installed headers are functional
g++ -std=c++2a -I$INSTALL/include -L$INSTALL/lib $CI/testlib.cc -lriscv -o /dev/null -include $BUILD/spike/install-hdrs-list.h

# run tests
time $INSTALL/bin/spike --isa=rv64gc $BUILD/pk/pk hello | grep "Hello, world!  Pi is approximately 3.141588."
time $INSTALL/bin/spike --isa=rv64gcv $BUILD/pk/pk vector-sum | grep "The sum of the first 1000 positive integers is 500500."
$INSTALL/bin/spike --log-commits --isa=rv64gc $BUILD/pk/pk atomics 2> /dev/null | grep "First atomic counter is 1000, second is 100"
LD_LIBRARY_PATH=$INSTALL/lib ./test-libriscv $BUILD/pk/pk hello | grep "Hello, world!  Pi is approximately 3.141588."
LD_LIBRARY_PATH=$INSTALL/lib ./test-customext $BUILD/pk/pk dummy-slliuw | grep "Executed successfully"
LD_LIBRARY_PATH=$INSTALL/lib ./test-custom-csr $BUILD/pk/pk customcsr | grep "Executed successfully"
Add basic continuous-integration flow 6 years ago			`#!/bin/bash`
			`set -e`

Build tests in CI rather than downloading a tarball from github 6 months ago			ROOT=`git rev-parse --show-toplevel`
			`NPROCS="$(nproc 2> /dev/null \|\| sysctl -n hw.ncpu)"`
			HERE=`pwd`
			`CI="$( cd "$( dirname "${BASH_SOURCE[0]}" )" >/dev/null 2>&1 && pwd )"`
			`INSTALL=$HERE/install`
			`BUILD=$HERE/build`
			`RUN=$HERE/run`
Add basic continuous-integration flow 6 years ago
Build tests in CI rather than downloading a tarball from github 6 months ago			`# build pk`
			`rm -rf $BUILD/pk`
			`mkdir $BUILD/pk`
			`cd $BUILD/pk`
			`git clone https://github.com/riscv-software-src/riscv-pk.git`
			`riscv-pk/configure --host=riscv64-linux-gnu --prefix=$INSTALL`
			`make -j$NPROCS`
			`make install`
Actually run a program in CI To avoid long CI times, keep the program in binary form. To avoid storing binary files in this repository, store the binaries as an asset on a github release. 4 years ago
Build tests in CI rather than downloading a tarball from github 6 months ago			`# build tests`
			`rm -rf $RUN`
ci: auto-generate per extension snippy tests This way adding new extension tests is as easy as adding 1 line script call and it is much harder to leave some instruction untested 4 months ago			`mkdir -p $RUN`
Build tests in CI rather than downloading a tarball from github 6 months ago			`cd $RUN`
			`riscv64-linux-gnu-gcc -static -O2 -o hello $CI/hello.c`
			`riscv64-linux-gnu-gcc -static -O2 -o dummy-slliuw $CI/dummy-slliuw.c`
			`riscv64-linux-gnu-gcc -static -O2 -o customcsr $CI/customcsr.c`
			`riscv64-linux-gnu-gcc -static -O2 -o atomics $CI/atomics.c`
Add simple vector extension test to CI 2 months ago			`riscv64-linux-gnu-gcc -static -O2 -march=rv64gcv -o vector-sum $CI/vector-sum.c`
Add github actions test that installed headers are usable 3 years ago
ci: add testing with llvm-snippy This commits adds basic spike testing using llvm-snippy random code generator. This initial testing runs spike on random valid code snippets and checks that it doesn't fail. Co-authored-by: Ksenia Dobrovolskaya <ksenia.dobrovolskaya@syntacore.com> 6 months ago			`# run snippy-based tests`
ci: auto-generate per extension snippy tests This way adding new extension tests is as easy as adding 1 line script call and it is much harder to leave some instruction untested 4 months ago			`wget https://github.com/syntacore/snippy/releases/download/snippy-2.1/snippy-x86_64-linux.tar.xz`
			`tar xf snippy-x86_64-linux.tar.xz`

ci: add testing with llvm-snippy This commits adds basic spike testing using llvm-snippy random code generator. This initial testing runs spike on random valid code snippets and checks that it doesn't fail. Co-authored-by: Ksenia Dobrovolskaya <ksenia.dobrovolskaya@syntacore.com> 6 months ago			`# test that snippy runs`
ci: auto-generate per extension snippy tests This way adding new extension tests is as easy as adding 1 line script call and it is much harder to leave some instruction untested 4 months ago			`bin/llvm-snippy --version \| grep "Snippy version: 2.1.0"`
			`PATH="$PATH:$RUN/bin" "$ROOT"/ci-tests/run-snippy-tests.sh "$RUN" "$ROOT"/ci-tests/snippy-tests "$INSTALL"/bin/spike`
ci: add testing with llvm-snippy This commits adds basic spike testing using llvm-snippy random code generator. This initial testing runs spike on random valid code snippets and checks that it doesn't fail. Co-authored-by: Ksenia Dobrovolskaya <ksenia.dobrovolskaya@syntacore.com> 6 months ago
Add github actions test that installed headers are usable 3 years ago			`# check that including sim.h in an external project works`
Build tests in CI rather than downloading a tarball from github 6 months ago			`g++ -std=c++2a -I$INSTALL/include -L$INSTALL/lib $CI/testlib.cc -lriscv -o test-libriscv`
			`g++ -std=c++2a -I$INSTALL/include -L$INSTALL/lib $CI/test-customext.cc -lriscv -o test-customext`
			`g++ -std=c++2a -I$INSTALL/include -L$INSTALL/lib $CI/custom-csr.cc -lriscv -o test-custom-csr`
workaround to support custom extensions that use standard prefixes RISC-V ISA states (21.1): "A standard-compatible global encoding can also use standard prefixes for non-standard extensions if the associated standard extensions are not included in the global encoding." Currently all the instructions (either from standard or custom extensions) are all being inserted into a single std::vector which is then being sorted. An instruction matching process performs linear search on that vector. The problem is that when a custom extension uses the same opcode as standard one (i.e. match and mask are equal to the standard counterparts) it is undefined which instruction will be picked. That is because in std::sort "The order of equal elements is not guaranteed to be preserved". That being said it is impossible to define custom extension (via customext) that would use the prefix of a disabled standard extension. In this change I separate custom and standard extensions in two separate std::vector's. By default we report an error if they have common elements (There're an additional processor_t constructor's argument that skips this check). If this error is disabled during instruction matching we first trying to find it among custom instructions. If it has been found the search is stopped and custom instruction is executed, otherwise we look for it among standard instructions. Overall this change does not completely fix the problem but at least makes it possible to use the feature of RISC-V ISA. 2 years ago
Check in CI that all installed headers are usable 2 years ago			`# check that all installed headers are functional`
Build tests in CI rather than downloading a tarball from github 6 months ago			`g++ -std=c++2a -I$INSTALL/include -L$INSTALL/lib $CI/testlib.cc -lriscv -o /dev/null -include $BUILD/spike/install-hdrs-list.h`
Check in CI that all installed headers are usable 2 years ago
Build tests in CI rather than downloading a tarball from github 6 months ago			`# run tests`
			`time $INSTALL/bin/spike --isa=rv64gc $BUILD/pk/pk hello \| grep "Hello, world! Pi is approximately 3.141588."`
Add simple vector extension test to CI 2 months ago			`time $INSTALL/bin/spike --isa=rv64gcv $BUILD/pk/pk vector-sum \| grep "The sum of the first 1000 positive integers is 500500."`
Build tests in CI rather than downloading a tarball from github 6 months ago			`$INSTALL/bin/spike --log-commits --isa=rv64gc $BUILD/pk/pk atomics 2> /dev/null \| grep "First atomic counter is 1000, second is 100"`
			`LD_LIBRARY_PATH=$INSTALL/lib ./test-libriscv $BUILD/pk/pk hello \| grep "Hello, world! Pi is approximately 3.141588."`
			`LD_LIBRARY_PATH=$INSTALL/lib ./test-customext $BUILD/pk/pk dummy-slliuw \| grep "Executed successfully"`
			`LD_LIBRARY_PATH=$INSTALL/lib ./test-custom-csr $BUILD/pk/pk customcsr \| grep "Executed successfully"`