topic Re: compiler lock up "internal error #413 please report to metrowerks" in 8-bit Microcontrollers

compiler lock up "internal error #413 please report to metrowerks"

jah — Fri, 15 Sep 2006 02:32:14 GMT

i have the following compiler for the mc9s08rd60dwe
codewarrior development studio for freescale hc(s)083.1 service pk fsicebase ver2

running on win xp + sp2

in a working and established main.c i add the code "while(1);"

and the compiler locks up and will not complete, it compiles w/o the while statement, and this code is used in several of our products for a year. i am using the while statement as a debug aid. the code does odd things when i place it in other areas of the code but it compiles. in the building screen (i only selected the compile icon) the Stop button has no effect?

Re: compiler lock up "internal error #413 please report to metrowerks"

jah — Fri, 15 Sep 2006 04:16:55 GMT

i might also add if i add the following to main.c
int i=1;
while(i);

the compiler takes the statement ok w/o error.

Re: compiler lock up "internal error #413 please report to metrowerks"

bigmac — Fri, 15 Sep 2006 10:17:01 GMT

Hello Jah,

I have previously gotten a compiler warning when using the while(1)... construct, but not compiler lockup. So I substituted the for( ; ; )... construct and this avoided the warning. I wonder if the compiler does not like there being nothing done within the infinite loop - I actually had some code within the loop.

Regards,

Mac

Re: compiler lock up "internal error #413 please report to metrowerks"

jah — Fri, 15 Sep 2006 21:32:07 GMT

for( ; ; )

did not work but

while(true==1)

did work

rough and wooly compiler

Message Edited by jah on 2006-09-15 09:33 AM

Re: compiler lock up "internal error #413 please report to metrowerks"

bigmac — Fri, 15 Sep 2006 21:53:32 GMT

Hello jah,

I am most surprised that the for() loop construct did not work, since this is used by the CW generated, default main() function, whenever a new project is created. There has to be another reason. As a matter of curiosity, what error or warning do you get for this method?

I guess that while(true==1) would be the same as writing while(1==1).

Regards,

Mac

Re: compiler lock up "internal error #413 please report to metrowerks"

jah — Fri, 15 Sep 2006 22:46:21 GMT

yes the for( ; ; ) did not work but the while(j==0) or while(true==1) works. in some of my other builds there is no error so down stream in the code there is some small black spot that triggers this.

i get "internal error #413" and some reference to a missing glbreg.c file on an F: drive. i never had a F: drive, nor do i want one.

is this only on codewarrior 3.0 and fixed on 5.0????

Message Edited by jah on 2006-09-15 10:50 AM

Re: compiler lock up "internal error #413 please report to metrowerks"

rocco — Sat, 16 Sep 2006 03:09:49 GMT

Hi, jah:

What are your optimization settings? Have you tried turning optimizations off?

It could be that CodeWarrior is having problems while optimizing, and the code optimizes to nothing.

Re: compiler lock up "internal error #413 please report to metrowerks"

jah — Sat, 16 Sep 2006 03:47:38 GMT

the while(1) causes the compiler is trying to remove dead code and gets into problems.

where is the adj for the compiler.