tree: a3e67f5f5c8fa21bd66126d7f2e79364689a7dd0 [path history] [tgz]
  1. cryptoc/
  2. eembc_coremark/
  3. google_googletest/
  4. patches/
  5. riscv_compliance/
  6. cryptoc.lock.hjson
  7. cryptoc.vendor.hjson
  8. eembc_coremark.lock.hjson
  9. eembc_coremark.vendor.hjson
  10. google_googletest.lock.hjson
  11. google_googletest.vendor.hjson
  12. meson.build
  13. README.md
  14. riscv_compliance.lock.hjson
  15. riscv_compliance.vendor.hjson
sw/vendor/README.md

Work with software code in external repositories

Please refer to vendor_hw for more details on rationale of vendoring external repositories.

RISC-V Compliance Suite

The RISC-V Compliance Suite defines a series of tests that to ensure the RISC-V system is complies with the RISC-V specification. Normally such a test would be run at the core level instead of the system level, but doing so confers advantages to ensure system integration did not alter the original properties of the core (for example breaking byte or half-word accesses).

To vendor in RISC-V Compliance Suite, please use the commands below.

./util/vendor_hw.py sw/vendor/riscv_compliance.vendor.hjson --verbose