Re: [lwip-devel] next_timeout not working correctly

[Bill Auerbach]

Hello,

You need to look at the map file and figure out the first and last variable
in BSS (if that's what they called it - whatever it is for uninitialized
variables).  A memset of 0 for that range of memory probably will suffice.
If you have control of the module ordering, you can create 2 source files
with an uninitialized global char in each to get the first and last variable
if you locate each module first and last respectively.  If you don't do this
I suspect there is more in lwIP that will not work.  None of us users know
because 99% of us have Standard C compliant compilers (or compliant startup
code to be technically correct).

I agree with Simon too.  I've seen all too many times something like:

unsigned char Buffer[1024] = { 0 );

Wasting 1k of flash when the { 0 } can be omitted.

Bill

-----Original Message-----
From: address@hidden
[mailto:address@hidden On Behalf
Of Carlos Galindo
Sent: Monday, November 03, 2014 1:56 PM
To: address@hidden
Subject: Re: [lwip-devel] next_timeout not working correctly

Hello Simon,
standard C does but not my MCU. It is mentioned in the compiler user's guide
of MCU:
<http://lwip.100.n7.nabble.com/file/n23455/5430.jpg>
Thus, I'm not sure how it will impact to the lwip code.
Best regards,
Carlos



--
View this message in context:
http://lwip.100.n7.nabble.com/next-timeout-not-working-correctly-tp23444p234
55.html
Sent from the lwip-devel mailing list archive at Nabble.com.

_______________________________________________
lwip-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-devel