[Icc-avr] Stack problems

[Albert vanVeen]

Many/most pascal compilers give you this sort of runtime checks. It may
be an overhead you can't always afford, but a great help for prototyping
(or some might say laziness).

Albert.
 

-----Original Message-----
From: icc-avr-bounces at imagecraft.com
[mailto:icc-avr-bounces at imagecraft.com] On Behalf Of Rich Webb
Sent: Tuesday, August 19, 2008 12:27 AM
To: icc-avr at imagecraft.com
Subject: Re: [Icc-avr] Stack problems

> A question: Does this mean that the compiler never have any control 
> over if the RAM used for local variables by a single function are more

> than total RAM-global variables? This is what happened. I couldn't see

> how this can be such a big deal for the compiler.

I would imagine that to install that large of a safety net would require
that the run-time image, and not the compiler, perform an explicit
boundary check after each and every operation that accessed (or could
access through indirection) any portion of the system RAM.

Not absolutely sure that I'd want that much of a performance cost,
although (especially for the JTAG-enabled AVRs) a compiler switch to
turn on such a feature may be useful. Dangerous, though, to depend on
something like that to catch problems after the fact.

_______________________________________________
Icc-avr mailing list
Icc-avr at imagecraft.com
http://dragonsgate.net/mailman/listinfo/icc-avr

Scanned by Bizo Email Filter