Closed YeuzhiHere closed 3 years ago
The popularity of a RISC-V based core is irrelevant for it to be a RISC-V Target. If sweRV EH1 is not a RISC-V target its not an issue. But if you want to validate sweRV EH1 core or use it as a RISC-V Target, you can look into Connect Riscof to SweRV EH2 core issue.
Targets are the responsibility of the model owners, not RISC-V. If you're developing a SWERV based core, you can create a target directory just as anyone else would do for their own implementation, and run the existing architectural compatibility tests on it. When V3 of the test framework becomes available, all target directories will be moved into the repos of the models themselves. This includes the 2 RISC-V sanctioned reference models, SAIL and SPIKE. Bilal's link above is a good place to start.
On Mon, Sep 20, 2021 at 10:48 PM Bilal Sakhawat @.***> wrote:
The popularity of a RISC-V based core is irrelevant for it to be a RISC-V Target. If sweRV EH1 is not a RISC-V target its not an issue. But if you want to validate sweRV EH1 core or use it as a RISC-V Target, you can look into Connect Riscof to SweRV EH2 core https://github.com/riscv-software-src/riscof/issues/10 issue.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/riscv-non-isa/riscv-arch-test/issues/212#issuecomment-923648607, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHPXVJSKI7RBKNFYYHFOZM3UDAMB7ANCNFSM5ENQQY6A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
Thanks both of you :)
Swervolf EH1 is very popular RISC-V based core. But In this repo, there is no target for swervolf EH1. Is there any specific reason? Kindly resolve this issue.