If you could guarantee that there are 255 unused bytes of SRAM below the lowest
stack location, maybe this would be OK.  But imagine the AVR sees an interrupt
just after __SP_H__ changes.  It begins by pushing a bunch of registers, which
clobbers the heap, or even worse writes to I/O space or the registers!

Jeff

Attachment: pgp7q7dc1wu1X.pgp
Description: PGP signature

_______________________________________________
AVR-GCC-list mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/avr-gcc-list

Reply via email to