• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 653 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.

C6000 linker internal error

CsabaP
Prodigy 230 points

Hi All,

 

Unfortunately  I've found new issues in the C6000 tool-chain (C64x+ target). The problem exists in 6.1.16., 6.1.18 and in 7.0.7.

Our C++ project compiles without errors, but the linker exits by internal error.

The code is good, it works perfectly by different other compilers (different gcc variants, msvc, etc..).

 

C:/ti/compiler_c6000/bin/cl6x -@ codec_package/compiler.opt -c main.c
Building server codec package (codec_package.x64P)

INTERNAL ERROR: c:\ti\compiler_c6000\bin\lnk6x.exe failed to allocate memory


This is a serious problem. Please contact Customer
Support with this message and a copy of the input file
and help us to continue to make the tools more robust.

make: *** [codec_package.x64P] Error 2

I'm trying to make a small test project to reproduce the bug, but it's not easy to simplify our rather large code.

It's a very critical bug for us. Please help me: if this bug seems similar for your eyes, please inform me what kind of code makes the linker to be failed.

I have several tips: to avoid the linker bug, I changed some codes in our project. Moving functions/methods from .cpp to . h temporarily helps.

 

As it's very critical to us, please feel free to write any ideas.

If you have a newer linker than the 7.0.4, please inform me.   If the CEO of  Texas Instr.  would like to link our libs to the codec engine by a hex editor and he can do it as a post-compile procedure in part of our build process, it's better than not to link at all.

(I know that this information is not too much, but until I can restrict/narrow the problem to a small code-base, I cannot send source files. If you wish, I can send the a64p files. They are are quite large: more than 150Mb. )

 

Thanks,

Csaba

  • 0
    TI__Guru**** 253230 points

    A recently released beta version of the compiler may help.  This wiki article shows how to obtain compiler releases.  Follow the link for free downloads.  On that page there is a link on the left for "Beta" releases.  On that page you will see v7.2.0 Beta 2 .  There is a good chance this release will work for you, but I cannot promise it.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Prodigy 230 points

    Hi, thanks, we'll try the new release.

     

    Our solution was adding the  --symdebug:none compiler option. By that the linker works.

     

  • 0 in reply to CsabaP
    Prodigy 100 points

    Hi

     

    I have just been experiencing a very similiar problem to the one described. I am building a code base in c++, that generates a large amount of object files. I did have the --symdebug:skeletal option, and changing this to :none has fixed my linker error.

    Thanks CsabaP!!!!

     

    I cannot navigate to the wiki page requested, to try the 7.2 beta, as this page responds with "You are not allowed to execute the action you have requested."

     

    Thanks

    Brett

     

     

  • 0 in reply to Brett Olsen
    TI__Guru**** 173310 points

    Brett,

    Sorry there was a problem with that wiki page. Please try the link again, it should work now.