-
• #2
Actually the
-Os
change was a mistake - I'd been doing some debugging trying to work out why the-Os
builds weren't reliable, and forgot to turn it off. JumJum noticed it in another thread too.Same thing with the code size growth. I'd accidentally committed a change to the Makefile. If you try now, I've backed it out so the compile size will have dropped back down.
-
• #3
Aaaha!
Cool, thanks. Updated the bigram binaries.
On July 8th, I cloned the Espruino repo, adjusted ESPRUINOBOARD.py for bigram, and built normally.
Today, noticing that v67 was out, I did the same, and noticed that the files were much smaller. I see that the default compiler flags were changed to -Os instead of -O3.
When I compiled with -O3, however, the binaries it produced were markedly larger than on july 8th (270k vs 240k) - I assume this is why the compiler flags were changed. I'm really curious as to what made the Espruino image so much larger; nothing on the changelog jumps out at me.
(Also - the binaries are on http://drazzy.com/espruino - Note that I changed the version back to v67, since it looked like the most recent commit to github just bumped the version)