• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 52 subscribers
  • Views 336 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

C optimization level used in building runtime support library (mklib)

ck.hk
Prodigy 220 points

Hi,

I am using CCS V5.2.0 Beta 2 installed with MSP430 option. I am wondering what is the optimization level used in building the C runtime support library. I am asking this question because it seems to me that some of the runtime support functions are not optimized.

I looked at the program "mklib.c" which is supposed to be used to build the runtime support libraries and the default options are:

" -o -oe -k -pdsw225 -q"

There are no options to turn on optimization (note that the switch for optimization is -O instead of -o).

If I want to compile the runtime support library with high optimization level, what should I do? Any ideas?

Thank you in advance.

  • 0
    TI__Intellectual 965 points

    For historical reasons, a lowercase -o BEFORE the linker -z/--run_linker switch is recognized the same as the uppercase -O, i.e. -o2 functions the same as -O2.  (A lowercase -o AFTER the -z/--run_linker switch is of course used to name the output file.)  This case insensitivity may not always be the case in the future, and uses should be changed to use the uppercase and documented form.  I don't know why mklib.c uses the lowercase form, and will look into it. 

    To respond to your issue, though, the -o in that list IS enabling optimization at the default level.