Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RISC-V #71

Open
dag7dev opened this issue Aug 26, 2020 · 8 comments
Open

RISC-V #71

dag7dev opened this issue Aug 26, 2020 · 8 comments

Comments

@dag7dev
Copy link

dag7dev commented Aug 26, 2020

What programming language should we add?
Risc-V

What is the official website for the language?
https://riscv.org/

Is this a language that comes in many variants? If so, which variant should we support?
Nope.

Does the language have an official logo?

Does the language have an unofficial logo?
it doesn't, but it has official variants, available at https://riscv.org/about/risc-v-branding-guidelines-and-materials/

Is there a testing framework available for the language?
Nope.

Is this language listed as 'supported' by Prism.js?
No.

If it is not supported by Prism.js, what is the closest supported language it maps to?
It is similar to MIPS.

Who will be leading the effort to launch the track?
Risc-v is becoming one of the most prominent language on the microprocessors.
It is provided under open source licenses that do not require fees to use, which is important because other architectures such as MIPS, it requires a paid license to be used.
Furthermore, everything is open source, you can watch sources here: https://github.com/riscv

@anthonygedeon
Copy link

Any updates on this proposal?

@kytrinyx
Copy link
Member

kytrinyx commented Jul 7, 2022

It looks like this proposal slipped between the cracks on our end. I'm so sorry about that!

In order to support the language we'd need two things:

  1. A testing framework, and
  2. Someone willing to take on the work of leading the development of the track.

We would help with understanding what needs to be done and how to do it.

@dag7dev
Copy link
Author

dag7dev commented Aug 25, 2022

A testing framework

no clues what you mean

@iHiD
Copy link
Member

iHiD commented Aug 25, 2022

@dag7dev How do you test your code works in RISC-V?

@dag7dev
Copy link
Author

dag7dev commented Aug 25, 2022

@dag7dev How do you test your code works in RISC-V?

usually by running it on Rars: https://github.com/TheThirdOne/rars

@iHiD
Copy link
Member

iHiD commented Aug 25, 2022

OK, so every exercise on Exercism has tests, which are run to see whether the student's code works or not. This is the code for x86-64-assembly which I guess is the closest to RISC-V: https://github.com/exercism/x86-64-assembly-test-runner

So the question Katrina is asking is how do we do that for RISC-V?

@dag7dev
Copy link
Author

dag7dev commented Aug 25, 2022

which I guess is the closest to RISC-V: https://github.com/exercism/x86-64-assembly-test-runner

it is

With an example it's more clear, thanks.

Can anyone fork that repo and make their changes based on risc things or another procedure is required?

I personally have no idea how to proceed talking from a dev perspective, but if someone can explain me more specifically what to do, I am happy to help.

Also, I can provide some examples + expected output!

@iHiD
Copy link
Member

iHiD commented Aug 25, 2022

That repository runs on our infrastructure and tests the students code. Try solving an exercise in the x86 track in the editor on Exercism's website to see how it feels to a student.

It might be useful for you to start by building hello-world exercise:

  • You need to create a stub file and a test file, and then a program that runs the tests to see if they work (that last bit is what the test-runner I linked to is doing effectively).

Here are the files for hello world in x86: https://github.com/exercism/x86-64-assembly/tree/main/exercises/practice/hello-world

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants