• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 1545 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.

[ProcessorSDK, OpenMP] .tdata and .tbss sections

Naoki Kawada
Guru 19890 points

Hi

My customer started to evaluate your OpenMP runtime (openmp_dsp_c667x_2_02_00_02) bundled in ProcessorSDK on C6678 EVM.

Some example codes are running correctly, but some warnings are present during the build process. 

warning #10247-D: creating output section ".tdata" without a SECTIONS specification
warning #10247-D: creating output section ".tbss" without a SECTIONS specification

Could you please let me know how we can handle these ?

Best Regards,
Naoki

  • 0
    TI__Guru** 116100 points
    Dear Naoki,

    Ask them to create a entry for ".tdata" and ".tbss" in *.cmd (SECTIONS) file of the project to avoid the warnings.

    Ex:
    SECTIONS
    {
    .text : load > DDR3 /* CODE */
    .data : load > DDR3
    .bss : load > DDR3 /* GLOBAL & STATIC VARS */
    RUN_START(bss_start),
    RUN_END(bss_end)
    .const : load > DDR3 /* SOFTWARE SYSTEM STACK */
    .cinit : load > DDR3 /* SOFTWARE SYSTEM STACK */
    .stack : load > DDR3 /* SOFTWARE SYSTEM STACK */

    .tdata : load > DDR3 //Titus
    .tbss : load > DDR3 //Titus

    }
  • 0 in reply to Titusrathinaraj Stalin
    Guru 19890 points
    Hi Titus S.

    Thank you for your quick reply.
    I agree with your suggestion. I believe the commands in *.cmd file will fix the warning itself, but I'm concerned putting these sections to DDR3 is correct/supposed to work with OpenMP runtime because these sections are not well known -- these are not C/elf standard sections.

    There are some memory declarations in system:

    name origin length used unused attr fill
    ---------------------- -------- --------- -------- -------- ---- --------
    L2SRAM 00800000 00060000 0002a9dd 00035623 RW
    OMP_MSMC_NC_PHY 0c000000 00020000 0000c4a8 00013b58 RW
    MSMCSRAM 0c020000 003e0000 0002ce88 003b3178 RW X
    DDR3 80000000 20000000 0800509a 17ffaf66 RW X
    OMP_MSMC_NC_VIRT a0000000 00020000 0000c4a8 00013b58 RW

    Putting these sections to DDR3 is really preferred in OpenMP environment ?
    Can you explain what is intended by these sections ? Or, do you have any documentations for that ?

    Best Regards,
    Naoki
  • 0 in reply to Naoki Kawada
    TI__Guru** 116100 points
    .tdata & .tbss sections seems to be sections of elf.
    refspecs.linuxfoundation.org/.../specialsections.html


    Putting these sections to DDR3 is really preferred in OpenMP environment ?
    Can you explain what is intended by these sections ? Or, do you have any documentations for that ?

    I can't comment anything on this.
    I would like you to suggest to post this question in TI E2E compiler forum.
    e2e.ti.com/.../343

    Refer to this e2e post.
    e2e.ti.com/.../1185420

    In my understanding, we can keep these sections into DDR as .bss section present in DDR3 for OMP examples.
    C:\ti\openmp_dsp_2_01_17_01\packages\examples\hello\omp_config.cfg
    They've kept ".stack" , ".args" & ".cio" in L2SRM, other than that all the sections were in DDR.
  • 0 in reply to Titusrathinaraj Stalin
    Guru 19890 points
    Hi Titus S.

    Sorry, I had a mis-understanding for tdata and tbss. You are right, these are elf sections.
    I close the thread.

    Thank you for your help.
    Naoki
  • 0 in reply to Naoki Kawada
    TI__Guru** 116100 points
    Dear Naoki,
    Thanks for your update.