stack/functions: Add functions lab.

[razvang0307]

Added functions lab based off old lab material.
Ignored throwback exercise 0.

Prerequisite Checklist

• Read the contribution guidelines regarding submitting new changes to the project;
• Tested your changes against relevant architectures and platforms;
• Updated relevant documentation (if needed).

Description of changes

Added the lab materials for function calls in assembly.

[github-actions]

Published at https://cs-pub-ro.github.io/hardware-software-interface/21/

[teodutu]

Things are looking nice so far. I highlighted what needs to be done in my inline comments and besides those, you should also do the following globally:

• Add a .gitignore file to all support/ and solution/ folders. This file should only exclude the executable file and not the object file (.o) because object files are already excluded by the .gitignore in the root of the repo.
• Take a look at the linter errors and fix them [1]. To fix the Spellcheck errors you'll also have to add the false positives (correct words flagged as incorrect because they're missing from the action's wordlist) to the wordlists here. Create a PR in which you add the new words to the corresponding files here [2]. After changing a file, run sort -u -f <file_name.txt> <file_name.txt> to remove duplicates. Remember to add the conjugations and declinations of each word as well as the word itself.
• Squash your commits into a single one as described here [3]. For further modifications, use git commit --amend --no-edit to add them to the existing commit.

[1] https://github.com/cs-pub-ro/hardware-software-interface/pull/21/checks
[2] https://github.com/open-education-hub/actions/tree/main/spellcheck/config
[3] https://www.freecodecamp.org/news/git-squash-commits/

[teodutu]

Increase the font of all text to 20 instead of 12.

[george-cosma]

Yhea, most of it is fine. Good work! I left some comments though that I'd like your input on. Feel free to disagree.

[george-cosma]

Oh, and one more comment: Do we need to put the content under Lab9/Functions/{Reading/Guides/...}. Shouldn't it be just Lab9/{Reading/Guides/...}, skip on the unnecessary sub-heading? This is a question to everyone - how do we want to handle this case?

[teodutu]

Oh, and one more comment: Do we need to put the content under Lab9/Functions/{Reading/Guides/...}. Shouldn't it be just Lab9/{Reading/Guides/...}, skip on the unnecessary sub-heading? This is a question to everyone - how do we want to handle this case?

Let's keep them all like this for now so all labs (with or without multiple subchapters) are consistent. It's easy to change this in the future so this isn't that big of an issue.

[savacezarmarian14]

Please check my comments. Also keep in mind that i didn't comment at all files that should have changes. IT LOOKS GOOD FROM MY POINT OF VIEW.

[teodutu]

ping @razvang0307