-
Notifications
You must be signed in to change notification settings - Fork 103
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
o1vm/riscv32im: adding programs for unit tests #2866
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2866 +/- ##
==========================================
- Coverage 72.04% 72.04% -0.01%
==========================================
Files 257 257
Lines 60690 60690
==========================================
- Hits 43723 43722 -1
- Misses 16967 16968 +1 ☔ View full report in Codecov by Sentry. |
935cd78
to
8e0a808
Compare
33438ae
to
77dc029
Compare
@@ -0,0 +1,17 @@ | |||
.global _start | |||
|
|||
exit_success: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: this is the semantics we do define in o1vm/riscv32im. It is not standard.
Solving conflicts. |
The idea is to move source files into a `src` directory at the same level than bin.
77dc029
to
710eaba
Compare
Done. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Noticed a few things when walking through the o1vm README
Co-authored-by: Martin Allen <31280145+martyall@users.noreply.github.com>
Co-authored-by: Martin Allen <31280145+martyall@users.noreply.github.com>
Co-authored-by: Martin Allen <31280145+martyall@users.noreply.github.com>
The idea of this set of changes is to introduce all the tooling that can be used by the developers working on the riscv32im to test the interpreter.
The set contains targets in the Makefile to compile the RISC-V GNU tool chain and some examples of basic programs written in the RISC-V 32IM ISA.
The test suite could contain actual functional tests, but also tests that should trigger exceptions or detect malicious prover/witness builders. The idea came out after witnessing these kinds of subtle changes.
The test related to o1vm/resources/programs/riscv32im/src/sll.S is commented for now because
lui
is implemented late in the @svv232 PR train (see #2852), and trying to rebase on top of his branch cause conflicts.I would suggest having this set of changes on master, and start integrating instructions by instructions, with their corresponding unit test? No strong opinion, but it helps to shape the correctness of the slightly bigger program which is fibonnaci.