Add arch-tests for Smcsrind and Sscsrind - Draft

[dansmathers]

Description

Add arch-tests for Smcsrind and Sscsrind fast-track extension
Note that these two indirect CSR extensions define a means to access
an array of registers via CSRs which will be defined by other extensions.
Until those other extensions are defined, the data read back is undefined.
So these arch tests primarily test the existence of the Smcsrind/Sscsrind
CSRs and access exceptions.

Related Issues

SAIL does not currently support Smcsrind, Sscsrind, Smstateen, Hypervisor mode.
Smcsrind/Sscsrind supported in spike: riscv-software-src/riscv-isa-sim@60c08b1
Sscsrind interaction with Smstateen still needs to be added to spike.

Ratified/Unratified Extensions

• Ratified
• [ X] Unratified

List Extensions

These extensions are described in the PDF spec available at:
https://github.com/riscv/riscv-smcntrpmf/releases/download/v1.0_rc4-frozen/riscv-smcntrpmf-v1.0_rc4.pdf

Reference Model Used

• [x ] SAIL
• [x ] Spike
• Other - < SPECIFY HERE >

Mandatory Checklist:

• [x ] All tests are compliant with the test-format spec present in this repo ?
• [ x] Ran the new tests on RISCOF with SAIL/Spike as reference model successfully ?

I will need help running coverage and other riscof infrastructure using spike only. SAIL is probably a long time from being able to support smstateen/hypervisor which is required by Sscsrind extension.

• Ran the new tests on RISCOF in coverage mode
• Link to Google-Drive folder containing the new coverage reports (See this for more info): < SPECIFY HERE >
• Link to PR in RISCV-ISAC from which the reports were generated : < SPECIFY HERE >
• [x ] Changelog entry created with a minor patch

Optional Checklist:

• RISCV-V CTG PR link if tests were generated using it : < SPECIFY HERE >
• Were the tests hand-written/modified ? Hand-written.
• Have you run these on any hard DUT model ? Please specify name and provide link if possible in the description
• If you have modified arch_test.h Please provide a detailed description of the changes in the Description section above.

[dansmathers]

Going to try creating a fork and then branches on that fork so I can have multiple non-interacting pulls. closing and will reopen as a new pull.