All code answer please show in the Rars software interface, assembly and run it to provide the details. Remember the code should be verified for correctness afterwards. Like input and output files with testing. Or provided in the Rars interface.

Could anybody help me?

RISC-V project - exercise 3 Write a program in RISC-V assembly using RARS. The program should not rely on uninitialized register values. The program should not contain any obviously inefficient actions. Do NOT use multiply/divide instructions for multiplication division by constants being powers of 2. Avoid the sequences of consecutive branches, esp. conditional branches followed by unconditional ones (unless necessary). All the text processing programs with file i/o should define getc and putc functions for single-character i/o, providing proper buffering of input and input operations with at least 512-byte buffers. Graphic programs should display images using MARS graphic display mapped to heap address range. A proper test data should be prepared, covering some interesting cases of program operation. 14. Write a program converting any file into a C language file representing the content of the original file as an array of bytes. The C program file should be properly formatted (16 bytes per line, offsets in comments before each 16 lines, total size in final comment. RISC-V project - exercise 3 Write a program in RISC-V assembly using RARS. The program should not rely on uninitialized register values. The program should not contain any obviously inefficient actions. Do NOT use multiply/divide instructions for multiplication division by constants being powers of 2. Avoid the sequences of consecutive branches, esp. conditional branches followed by unconditional ones (unless necessary). All the text processing programs with file i/o should define getc and putc functions for single-character i/o, providing proper buffering of input and input operations with at least 512-byte buffers. Graphic programs should display images using MARS graphic display mapped to heap address range. A proper test data should be prepared, covering some interesting cases of program operation. 14. Write a program converting any file into a C language file representing the content of the original file as an array of bytes. The C program file should be properly formatted (16 bytes per line, offsets in comments before each 16 lines, total size in final comment