• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 2089 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

"#10068-D no matching section" for .bss section in C6000 CSL

Michael S
Mastermind 21285 points


Hi team,

I've ran into a small warning message that is actually throwing a red flag (at least to me).  In a linker configuration file, I see this

and the warning thrown back to me is 

"../xgac.cmd", line 81: warning #10068-D: no matching section

To my understanding any uninitialized globals and statics should be placed into the .bss sections and any library that has globals, which this does, should have a .bss section produced by the compiler.

What I've done -

Checked that  the section names were not changed between revisions.  Earliest available  version of the C6x compiler docs call this section .bss so that's a no-go. 

Checked the C6 CSL source and the resulting assembly.  There are plenty of globals in the library source that are not declared as FAR and so these should be sectioned into .bss.

Granted, the CSLs were last built using older tools but as since the sections have not changed names, this warning should not occur.

  • 0
    TI__Guru**** 251490 points

    One of two things happened.

    One, none of the variables in the .bss and .far sections of the csl6415.lib library are ever used.  In that case, the .cslbss section is legitimately empty.  You can ignore the diagnostic.

    Two, the .bss and .far input sections from csl6415.lib somehow became part of a different output section, and thus are probably placed in memory somewhere else.  

    You can tell the difference by inspecting the map file and searching for any .bss or .far input sections from csl6415.lib.  If you don't find any, it is the first scenario (OK).  Otherwise, it is the second scenario (bad).  

    If it is the second scenario, you need to see which output section is including .far and .bss from csl6415.lib and why.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    TI__Mastermind 21285 points

    Situation 1.  No .bss-placed symbols to link in.

    Thanks George.