Weird compiling error (occurs in the 1st time compiling, but is gone in the 2nd time compiling)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Weird compiling error (occurs in the 1st time compiling, but is gone in the 2nd time compiling)

Jump to solution
2,168 Views
xuedongyang
Contributor II

Hi, NXP experts,

I observed a weird thing: sometimes, when I built a project, I observed this compiling error. But when I built it again, the problem was gone. It is very annoying.

Any idea what could be the cause and how to fix it?

xuedongyang_0-1674485531351.png

Thanks,

Xuedong

 

0 Kudos
Reply
1 Solution
2,122 Views
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Should be a problem related to compiler (as you shown in the image)

Maybe it does not like the reference to be without an absolute number. But again, seems to be more complicated than that.

Still, good to know you got it working.

View solution in original post

0 Kudos
Reply
3 Replies
2,127 Views
xuedongyang
Contributor II

Thank you for the suggestion, Daniel.

I did closing non-related projects, but the problem still occasionally happened.

We tried to replace "ldA [a0]" with "ldA [a0]+0". Looks like this fixed the problem. We never saw the problem since we did the replacement of the instruction. However, we don't have explanation why this fixed the problem.

Any thought?

0 Kudos
Reply
2,123 Views
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Should be a problem related to compiler (as you shown in the image)

Maybe it does not like the reference to be without an absolute number. But again, seems to be more complicated than that.

Still, good to know you got it working.

0 Kudos
Reply
2,142 Views
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

Could be that the project is still loading the references. We do recommend closing non-related projects due to them sometimes carrying errors to your current project.

Please, let us know.

0 Kudos
Reply