To go in the docs: (once other pull requests are merged)
In the test.py script, when running testcases, we make a call to the GCC-RISC-V compiler and output the compiled test programs as .gcc.s. Your compiler may not produce the exact same assembly as GCC, so it's not advisable to blindly attempt to replicate the GCC output. Instead, the purpose of the .gcc.s files is to assist in debugging issues within your own compiler.
To go in the docs: (once other pull requests are merged)
In the test.py script, when running testcases, we make a call to the GCC-RISC-V compiler and output the compiled test programs as.gcc.s. Your compiler may not produce the exact same assembly as GCC, so it's not advisable to blindly attempt to replicate the GCC output. Instead, the purpose of the .gcc.s files is to assist in debugging issues within your own compiler.