4.1.4 Compiler Optimization -O 2 (Eclipse)

I tried the new compiler option in Eclipse.

All of a sudden I have about a dozen compiler errors! :-) That's a good thing. Probably poor coding technique it detected. GREAT! Time to go fix my app!!

Thanks Garmin - moving in the right direction.

Now give us access to a few more device features, Like the current gradient, please :-)

Top Replies

jim_m_58 over 4 years ago in reply to DaveBrillhart +1

Tired one of my apps with just -l0 and again with -L0 -O2 and the results were the same. Maybe a typo in the email?

With the same app, I do notice a small savings with the beta 4.1.4 compiler and the production…
jim_m_58 over 4 years ago in reply to DaveBrillhart +1

Barrels get compiled when you compile the app that uses them. If you look at a .barrel file, it's just a zip of the barrel project

All Replies

Shent-Aurkhan (SHN) over 4 years ago

Hi, since you are still in Éclipse like me, could we use the -l 0 and the -O 2 at the same time? If yes could you please tell me how to put it?

DaveBrillhart over 4 years ago in reply to Shent-Aurkhan (SHN)

Options are in Preferences in Connect IQ, compiler options. By memory. I used -O 2. Not sure about using both.

jim_m_58 over 4 years ago in reply to DaveBrillhart

For me, in Eclipse. I use -L0 as I don't use type checking. -O2 is the default for optimization, so I don't include that, and optimization is done.

Shent-Aurkhan (SHN) over 4 years ago in reply to jim_m_58

oh yes sorry that was written that -O2 is the default... so no need to put it...

jim_m_58 over 4 years ago in reply to Shent-Aurkhan (SHN)

Based on your code, and how optimized it is already, you might seen only a minor gain with optimization on. I see less than 100-200 bytes in somethings.

Shent-Aurkhan (SHN) over 4 years ago in reply to jim_m_58

just tested and no difference... not even 100bytes.

But if I may, I tested -l 1 and of course lots of issue, it seems like if you put é instead of Time.FORMAT_LONG it is an issue?!

DaveBrillhart over 4 years ago in reply to jim_m_58

Hi Jim! The e-mail I got from Garmin about this new Beta Compiler suggested we need to add the -O 2 for max optimization. Are you sure that is the default, and no need to add that option? If so, then using -O 1 or -O 0 is used to reduce the default of max optimization? Thanks!

jim_m_58 over 4 years ago in reply to DaveBrillhart

Tired one of my apps with just -l0 and again with -L0 -O2 and the results were the same. Maybe a typo in the email?

With the same app, I do notice a small savings with the beta 4.1.4 compiler and the production one

_psx_ over 4 years ago in reply to jim_m_58

Savings depends on code, if somebody had to optimize code due to the problems with memory (especially in the same area new compiler does) savings will be minimalistic

I have a lot of const, enums and compilers can save 2,5kB in one apps and 0,1 in second one where I've put into code all const myself {and now regret).

DaveBrillhart over 4 years ago in reply to jim_m_58

Hi Jim. So I selected the Beta SDK. Rebuilt my four barrels. Then fixed the code issues it found. Ran it in my simulator. All good. Tried to EXPORT it. No joy. Beta exports are not allowed. So going back to the production 4.1.4 SDK. Any issue using those newly compiled barrels I built with the Beta SDK? Seems to work. Maybe barrels aren't really compiled.