AM64: dhrystone_benchmark example for A53 core fails in debug mode

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Medium
    • SITSW-10185
    • 11.02.00
    • 12.00.00
    • am64xx-sk

      dhrystone_benchmark example for A53 core fails in debug mode with following error message:

       

      Measured time too small to obtain meaningful results
      Please increase number of runs 

      It seems that debug mode has a higher optimization level compared to release for this example, this is because in CFLAGS_common -O3 is the make file for dhrystone_benchmark (for nortos, freertos , feertos-smp) while optimization for release mode is set to -O2:

      https://github.com/TexasInstruments/mcupsdk-core/blob/next/source/dhrystone_benchmark/makefile.am64x.a53.gcc-aarch64.freertos#L51 

      https://github.com/TexasInstruments/mcupsdk-core/blob/next/source/dhrystone_benchmark/makefile.am64x.a53.gcc-aarch64.freertos-smp#L51 

      https://github.com/TexasInstruments/mcupsdk-core/blob/next/source/dhrystone_benchmark/makefile.am64x.a53.gcc-aarch64.freertos-smp#L51 

      Removing this -O3 from CFLAGS_common resolves this issue and set correct optimization levels for debug and release binaries.

       

            Assignee:
            TI User
            Reporter:
            TI User
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                Connection: Intermediate to External PROD System
                EXTSYNC-6522 - AM64: dhrystone_benchmark example f...
                SYNCHRONIZED
                • Last Sync Date: