Replies: 1 comment
-
Thanks! I need update the tools here too! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I suppose the safe bet is to compile with the project's recommended compiler but some people might be doing some code experiments. To save anyone some time, there's a couple of small snags if compiling code with > gcc 12.
csrr and csrw psuedo opcodes have been deprecated by default after v12 i think. You can add the arch suffix to add them back e.g. ARCH=rv32e_zicsr (see src/makefile)
debug info strings seem to be compiled in by default. not sure if this is just for gcc versions > 12. It means that the data section (RAM) ends up bloating out by 30KB or something for what should be much smaller for the example code projects. Try adding -gtoggle as a compiler option to stop it from doing this if you don't have the ram space for them.
JD
Beta Was this translation helpful? Give feedback.
All reactions