Hello, José,
Saturday, January 25, 2003, 7:11:36 PM you wrote:
JS> I have tried to compile the tcpip stack for the MSP430F149 written by
JS> Andreas Dannenberg under msp430-gcc 3.2 and have found that if I use the -O
JS> option, the program does not run, however, compiling without the -O option
JS> produces code that runs. The same code compiles OK with the IAR suite with
JS> or without optimization.
JS> The problem that I have noticed-patiently using msp430-gdb (Insight) 5.1.1--
JS> is that the frame that the stack sends in response to, say an ECHO request,
JS> is corrupt when the code is compiled with the -O option and is OK with no
JS> optimization.
JS> I have not been able to pin point what is actually failing, although it
JS> seems that either the memcopy() function or the *(unsigned int *) casting
JS> used in the function that assembles the return frames in tcpip.c is failing
JS> under optimization.
JS> I am attaching the code in case someone wishes to look into the optimization
JS> issue.
JS> Thanks,
JS> José Sacerio
There was some problems with optimization, mostly with inlined
functions (like memcpy() compiled to series mov instructions), but
all was fixed some days ago, and easyWEB compiles now successfully
and works correctly. Get fresh sources from CVS, compile and enjoy
:)
Victor.
