Re: Floating point calculations on 16 uC

cbarn24 wrote:
>You dont say what kind of garbage your getting. Stack overruns are easy
>to detect as it will trash your fixed variables starting from the
>highest 1 (check your map file). Sometimes you can have problems with
>far/near pointers. Compile useing the large model and see if your
>problem dissapears. If all else fails disable each interrupt
>individualy.

I don't think it's stack overflow. I have a "stack used" funtion and it
reports almost 3KB not used. My memory model is currently medium. Can
you explain in more detail why this will effect the floating point
variables. Note that this only happens intermittently. Usually the
results are correct. Thanks

.

Relevant Pages

  • Re: How does Win32 implement assembly language sections?
    ... means all segments are set to the same address. ... not used in FLAT memory model. ... The stack is defined in a PE file in the "Stack Reserve" and "Stack ... You normally think of FLAT memory model in win32 as a linear address ...
    (comp.lang.asm.x86)
  • Re: Heap Vs Stack
    ... if i refer the C memory model, ... other memory area. ... Does any limit exist upto which a stack or a heap can grow. ...
    (comp.lang.c)
  • Re: Heap Vs Stack
    ... if i refer the C memory model, ... Does any limit exist upto which a stack or a heap can grow. ... (for example a Windows or Unix programming ...
    (comp.lang.c)
  • Re: 4GB VM for 32 bit processes
    ... It works on Linux, but I don't know about other Un*x ... Unfortunately, I don't have access to a HP-UX, so I ... > implements the symmetric-version of the memory model supported by the ... > user_space and stack growths towards higher addresses). ...
    (comp.unix.programmer)
  • Heap vs Stack
    ... if i refer the C memory model, ... other memory area. ... Does any limit exist upto which a stack or a heap can grow. ...
    (comp.unix.programmer)