[En-Nut-Discussion] Re: Problems with TCP reception

[Alexander Baranov]

If a global variable can be unobvious modified,  for example, in an
interrupt routine - it should be declared as volatile. Then the compiler
will not try to optimize it out.
Alexander

> Hi again,
>
> I don't think NutSegBufEnable is the problem. In fact, I use practically
the
> same way to send 480000 bytes over ethernet (Http) and there is no errors.
> I've been testing it and it seems the problem could be in the "code
> compressor" optimization. I have read (no idea where), that global
variables
> should be declared as "volatile" to avoid the optimizer to re-use them.
Any
> notice about it?
>
> Thx again,
>
> Eduardo
>
> > Message: 1
> > Date: Thu, 14 Apr 2005 12:33:31 +0200
> > From: Harald Kipp <harald.kipp at egnite.de>
> > Subject: Re: [En-Nut-Discussion] Problems with TCP reception
> > To: "Ethernut User Chat (English)" <en-nut-discussion at egnite.de>
> > Message-ID: <5.1.1.6.0.20050414122544.03660e20 at egnite.de>
> > Content-Type: text/plain; charset="us-ascii"; format=flowed
> >
> >
> > As long as NutTcpReceive() returns a positive value, you can
> > be fully sure, that no data will ever get lost on the TCP
> > transfers.
> >
> > Possibly the problem lies in buffer handling. NutSegBufEnable?
> >
> > Harald
> >
> >
> >
>
> _______________________________________________
> En-Nut-Discussion mailing list
> En-Nut-Discussion at egnite.de
> http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion
>
>