Skip to main content

[archive] option -Zc

  • April 3, 2008
  • 3 replies
  • 0 views

[Migrated content. Thread originally posted on 02 April 2008]

Hello to all,

I'm testing the -Zc option, in project settings, compiler -> miscellaneous options.

"Optimize for smaller code instead of faster code (-Zc)"

Normally, we have active this option, reducing the memory in disk that acu programs need but reducing speed of execution too. At least is what I undestand from the option text. But i deactivate that option and compiling i see that my acu programs goes from 350 kb to 342 kb (for example) in disk space, then... i have doubts... This option really exchange speed for memory in disk and viceversa?

Thanks afterwards

3 replies

[Migrated content. Thread originally posted on 02 April 2008]

Hello to all,

I'm testing the -Zc option, in project settings, compiler -> miscellaneous options.

"Optimize for smaller code instead of faster code (-Zc)"

Normally, we have active this option, reducing the memory in disk that acu programs need but reducing speed of execution too. At least is what I undestand from the option text. But i deactivate that option and compiling i see that my acu programs goes from 350 kb to 342 kb (for example) in disk space, then... i have doubts... This option really exchange speed for memory in disk and viceversa?

Thanks afterwards
Smaller code instead of faster implies that the codesegment may be reduced. I say may be because it is very code dependent on whether it can be optimized or not.
A program that basically does a lot of file IO will for instance not make much of a difference because the file IO does not leave much room for variations.
Math and string handling are areas in which optimization should make a difference, but again, it is a matter of volume to be able to see significant differences.
I agree however, that it is not exactly what your result is not exactly what you would expect.
I suggest you send it to tech support to get an explanation.

[Migrated content. Thread originally posted on 02 April 2008]

Hello to all,

I'm testing the -Zc option, in project settings, compiler -> miscellaneous options.

"Optimize for smaller code instead of faster code (-Zc)"

Normally, we have active this option, reducing the memory in disk that acu programs need but reducing speed of execution too. At least is what I undestand from the option text. But i deactivate that option and compiling i see that my acu programs goes from 350 kb to 342 kb (for example) in disk space, then... i have doubts... This option really exchange speed for memory in disk and viceversa?

Thanks afterwards
Yeah, we are looking to get an upgrade in speed for our acus, no matter if they grow a bit in disk space, but seeing that they loss size... when they must grow up... i'm a bit lost.

I'll advice the tech team. Thanks Gforseth.

[Migrated content. Thread originally posted on 02 April 2008]

Hello to all,

I'm testing the -Zc option, in project settings, compiler -> miscellaneous options.

"Optimize for smaller code instead of faster code (-Zc)"

Normally, we have active this option, reducing the memory in disk that acu programs need but reducing speed of execution too. At least is what I undestand from the option text. But i deactivate that option and compiling i see that my acu programs goes from 350 kb to 342 kb (for example) in disk space, then... i have doubts... This option really exchange speed for memory in disk and viceversa?

Thanks afterwards
Yeah, we are looking to get an upgrade in speed for our acus, no matter if they grow a bit in disk space, but seeing that they loss size... when they must grow up... i'm a bit lost.

I'll advice the tech team. Thanks Gforseth.