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.

Compiler/CODECOMPOSER: INTERNAL ERROR!: <LABEL_A> defined differently in each pass

Part Number: CODECOMPOSER

Tool/software: TI C/C++ Compiler

Hi

I am developing a firmware for PRU-ICSS and have run into a compilation issue as shown below. My compiler version in 2.1.5 & am using CCSv7.3 :

>> Compilation failure
subdir_rules.mk:9: recipe for target 'Micro_Scheduler.obj' failed
"switch_MII_Xmt.asm", INTERNAL ERROR!: LABEL_A defined differently in each pass

This may be a serious problem. Please contact customer support with a
description of the problem and a sample of the sourcefile that caused this
message to appear.


Sample snapshot of the firmware code has been provided below:

LABEL_B:

JMP to some other function

.if $isdefed("SYMBOL_A")

QBBC LABEL_A

...

QBBS LABEL_B

LABEL_A:
.endif ;SYMBOL_A


Hope someone knows the fix. Kindly let me know if more debug info required to root cause this issue.

FYI, I have read though https://e2e.ti.com/support/development_tools/compiler/f/343/t/199063 

  • Hi

    Found the issue & fixed it. Apparantly, the e2e link above helped in root causing the issue. How I understand it now is : Somewhere in my firmware forward declaration of a symbol is happening & it is generating this unrelated error.

    The fix was in one of the lines b/w QBBC LABEL_A & QBBS LABEL_B


    Thanks.

    Is it possible to have a proper build error reported wrt to this issue?

     

  • I don't understand what happened.  I'd appreciate if could get a test case which allow me to reproduce this ...

    Garvit Jain said:
    subdir_rules.mk:9: recipe for target 'Micro_Scheduler.obj' failed
    "switch_MII_Xmt.asm", INTERNAL ERROR!: LABEL_A defined differently in each pass

    I presume this means the source Micro_Schedule.asm is being built.  This file includes switch_MII_Xmt.asm.  Please submit those files, and any files included by them.  I also need to see the exact build command.  Please copy-and-paste that from the CCS Console view.

    Thanks and regards,

    -George

  • Thank you for sending a test case through other channels.  I can reproduce the problem.  I filed CODEGEN-4645 in the SDOWP system to have this investigated.  You are welcome to follow it with the SDOWP link below in my signature.

    Thanks and regards,

    -George