Being used to working with the ChipworkX I learned a hard lesson about restricted resources today
At first my elf image was about 52kb, then after passing the -Os and -g0 options to the compiler,
I got reduced to about 39kb.
Later I noticed that the use of constants and the use of long variable names also increases the size of the image. The constants… that made sense… but the variable names?
Why doesn’t the compiler simply convert them to something very short so the code can stay clean
while keeping things small ?
I mean is this why C developers write ugly looking code?
So I have a few questions here
- What can I do to keep my elf image as small as possible, do I really need to write ugly code?
- What is the best way to load the bytes of the elf image, as I’m always running out of memory. Even if I use Debug.GC(true) before and after loading the bytes using File.ReadAllBytes
- What is the max size of en elf image that can (in your experience) be loaded on a Fez Panda II