• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 619 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.

EALLOW and -o4 not playing nicely

erich.gluck
Prodigy 120 points
Other Parts Discussed in Thread: TMS320F28335

Greetings,

I am programming for a TMS320F28335 in Code Composer v5.1.0.09000 and am going through a fairly finished product to look for some places I could optimize. One of the main concerns I have is that I have about 10 files that throw the remark "#1463-D Link-time optimization is disabled for this file due to the use of inline assembly" due to using EALLOW and EDIS in their initialization functions.

My questions are:

Does this affect the optimization of the file in compile-time? (I believe it does not)

Would it be profitable to me speed-wise to create a separate file that only contains the EALLOW/EDIS functions redefined to force all the disabling of the optimizations to a file that I don't care about? (e.g. function below)

void my_eallow(void)
{
    EALLOW;
}

Thanks,

Erich

  • 0
    TI__Guru**** 232700 points

    erich.gluck said:
    Does this affect the optimization of the file in compile-time?

    No.  In effect, the optimization level of those 10 files is changed from --opt_level=4 to --opt_level=3.

    erich.gluck said:
    Would it be profitable to me speed-wise to create a separate file that only contains the EALLOW/EDIS functions

    In theory, yes.  In practice, it is not as clear.  The only way to know is to try it.

    Thanks and regards,

    -George