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.

Different Release build output between back to back builds on same PC with same source and compiler version REVISITED.



Back in October of 2013 I posted an issue with inconsistent builds when using the same PC, same source code, same compiler, etc. Basically I can build, clean, and build and get a different size output. At the time I used the ofd6x.exe to try to identify where the extra size was coming from with little luck. After a TI person reviewed my issue they suggested that I turn off program compilation mode (-pm). At the time it appeared to fix the issue and I went happily on my way, until now. I am having a similar issue. We have moved from DSP/BIOS to SYS/BIOS in the since October but now I'm getting inconsistent builds. As I said in October when we were using 5.2.5 version of the compiler we had no problem but when we went to 6.x.x is when this began. We're using 6.1.3. I again used ofd6x.exe to identify the size change and this time it is in

xdc_runtime_Startup_startMods__I          one has a size of 127 and the other build has a size of 125      

 

  • Darrin,

    There could potentially be a few sources of error here.  For example, this could be introduced by the CCS Project Manager, the compiler, or the XDC tools.  Can you please attach some additional logs from back-to-back builds exhibiting the issue.  In particular, could you attach a zip file containing the following:

    1. A text file for each build capturing the complete command line output in the build window.
    2. The output map file for each build.
    3. Optionally the actual executable (*.out file) might prove useful.  If nothing else please set it aside in case I need you to send it to me (outside the forum) later for further debug so you don't have to repeat this work.

    Brad

  • Brad,

     

    Thanks for the quick reply. I have the .map and .out files available, but not the build log, I can send you immediately. I will have to capture the text during a build. However, I will be away for 2 weeks so I'm not sure how to proceed. I will continue to address this issue on my return. What would you recommend I do? Wait to follow up when I return?

  • I recommend we pick it back up when you're back.  Once you get a chance to capture the data (including the command line) then you can attach a zip file to the post using the "Options" menu in the forum.

  • Brad,

    Sounds great, thanks.

     

    Darrin