• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 52 subscribers
  • Views 626 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.

RTTI performance penalty - EABI/ELF

Joachim Siegler
Intellectual 765 points

Hi Guys,

I read about the performance penalty caused by the use of RTTI and exeptions within COFF.  LINK

In this post a TI employee wrote that the performance penalty caused by the use of exceptions within the EABI/ELF is significantly lower as with COFF. What I'm looking for is a comparision of the performance penalty caused by the use of RTTI with COFF and EABI/ELF.

Thanks,
Jo

  • 0
    TI__Guru**** 245170 points

    The overhead of using RTTI is entirely in memory footprint.  There is no overhead in cycles.  You can see memory footprint by looking at the linker map file.  Though many find it more convenient to use sectti from the cg_xml package.  Build your app with and without --rtti, and note the difference in memory footprint.  I expect it will be a few percent.  But the only way to be sure is to measure it.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Intellectual 765 points

    Hi George,

    Thank you for your answer. Excuse me, please, that I forgot to verify your answer.

    - Jo