Changes in size of Espruino binary? #3942
Unanswered
espruino-discuss3
asked this question in
General
Replies: 1 comment
-
Posted at 2014-07-14 by @gfwilliams Actually the 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. Posted at 2014-07-14 by DrAzzy Aaaha! Cool, thanks. Updated the bigram binaries. |
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
Uh oh!
There was an error while loading. Please reload this page.
-
Posted at 2014-07-14 by DrAzzy
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)
Beta Was this translation helpful? Give feedback.
All reactions