The TI E2E™ design support forums will undergo maintenance from Sept. 28 to Oct. 2. If you need design support during this time, contact your TI representative or open a new support request with our customer support center.

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.

TMS320C6745: How to remove .fphead information from disassembly

Part Number: TMS320C6745

I am looking at the disassembly generated by Code Composer. There is a line

E1200083 .fphead n,l,W,BU,nobr,nosat,0001001

This is not a 'real' instruction as far as the processor is concerned, but rather it is informational. 

Does anyone know the compiler/build/link option that disables this?

I need it removed from the final MyProgram.out file that is generated.

Thanks!

  • This is not a 'real' instruction as far as the processor is concerned, but rather it is informational.

    It is not an instruction in the same sense as an ADD instruction.  But it is present in memory (it takes up 32-bits), which gives information to the CPU, which the CPU then acts on.  So, if you expand your expectation of what counts as an instruction, then a fetch packet header is a real instruction.  For more background, please see this forum thread.

    That being the case, there is no way to get rid of .fphead.  But I have two suggestions for you to consider.

    One ... Look at the assembly code generated by the compiler.  A good way to do that is by using the compiler option --src_interlist.  It causes text files with the extension .asm to appear in the folder named after the current build configuration (typically Debug). 

    Two ... Use the standalone disassembler.  It is named dis6x.  It is located in the same directory as the compiler cl6x.  From a command line interface, run a command similar to ...

    dis6x file.out | findstr /v fphead

    Change file.out to the name of the final executable file created by the linker.  The command findstr is built into Windows.  If you are on a Linux system, use fgrep -v instead.

    Thanks and regards,

    -George