Compiled code statistics #52
Description
Low priority, but at some point in the future we should add a way to measure compiled code (by students' compiler) statistics, like binary size / # of machine instructions, simulated cycles, actual compilation time. These would allow for a better reasoning about any of the implemented "optimisations extensions", once we put more focus on extensions in our grading.
That could be implemented behind a CLI flag (--analyse_binaries?)