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

Support of specific runtime configurations #36

Open
moalshak opened this issue Dec 20, 2022 · 3 comments
Open

Support of specific runtime configurations #36

moalshak opened this issue Dec 20, 2022 · 3 comments

Comments

@moalshak
Copy link

moalshak commented Dec 20, 2022

For example :

  • max number of X instruction.
  • a max run time, after which the program gets killed and is flagged inefficient
@moalshak
Copy link
Author

I would say that gathering a lot of metadata about the ran program would be quite helpful as well.

@chiragsakhuja
Copy link
Owner

Could you explain a use case for the first bullet point?

max number of X instruction.

Also, could you give an example of what kind of metadata should be collected?

@moalshak
Copy link
Author

moalshak commented Dec 21, 2022

We are using LC3 at the university of Groningen, and I am writing test-cases for students using our online program tester (called Themis).
One of the assignments is to write an efficient multiplication program by choosing the smaller number as the counter for the repeated addition. I wanted to know exactly how many times the students used the ADD instruction in their program, but I could not out of the box.

Also, could you give an example of what kind of metadata should be collected?

I think that for teachers, it is best if all metadata that can be collected, gets collected. This way, teachers can write very specific test cases that the students code has to adhere to. For example, how often a register was read, how often the memory was read, how often the code branched and to what label.

But at the bare minimum, how often every instruction was executed.

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

No branches or pull requests

2 participants