Uploaded image for project: 'Embedded Software & Tools'
  1. Embedded Software & Tools
  2. EXT_EP-10085

Code coverage symbols not defined when profile counter section manually placed

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • Code Generation Tools
    • CODEGEN-8216
    • Hide
      ARMCLANG_2.1.0.LTS
      ARMCLANG_1.3.0.LTS
      ARMCLANG_2.1.2.LTS
      Show
      ARMCLANG_2.1.0.LTS ARMCLANG_1.3.0.LTS ARMCLANG_2.1.2.LTS
    • Hide
      ARMCLANG_1.3.2.LTS*
      ARMCLANG_2.1.3.LTS*
      Show
      ARMCLANG_1.3.2.LTS* ARMCLANG_2.1.3.LTS*
    • default
    • Hide
      The workaround is that the client either shouldn’t explicitly place the section, or if it does, the symbols should also be explicitly defined based on the section location.  If users don't explicitly place the section, the linker will place it based on the location of the .bss section.
      Show
      The workaround is that the client either shouldn’t explicitly place the section, or if it does, the symbols should also be explicitly defined based on the section location.  If users don't explicitly place the section, the linker will place it based on the location of the .bss section.

      In looking at the linker, it appears that if the _llvm_prf_cnts section is explicitly placed by the linker command file, then the “start_llvm_prf_cnts" and "stop__llvm_prf_cnts" symbols are not created. 
      The workaround is that the client either shouldn’t explicitly place the section, or if it does, the symbols should also be explicitly defined based on the section location.  If users don't explicitly place the section, the linker will place it based on the location of the .bss section.

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

              Created:
              Updated:
              Resolved: