Renamed rv32e_unratified to rv32e_m because E extension was ratified …

[davidharrishmc]

…January 2023

Description

Renamed rv32e_unratified to rv32e_m because E extension was ratified January 2023

Related Issues

NA

Ratified/Unratified Extensions

• [ E ] Ratified
• Unratified

List Extensions

E

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 ?
• [ n/a] Ran the new tests on RISCOF in coverage mode
• [ n/a] Link to Google-Drive folder containing the new coverage reports (See this for more info): < SPECIFY HERE >
• [ n/a] 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 ?
• [ y openhwgroup/cvw] 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.

[allenjbaum]

This covers all the base ISA ops, and a few other extensions as well. RV32E may require effectively all extensions to be supported, but we are not prepared to do this at this time (and possibly won't have to; clarification has been asked for).
To properly test this, Zicsr must be implemented as well, which is a bit problematic (this PR does have that support, as does RV32I, so that should be OK)