--- Comment #6 from darkdragon2000 at hotmail dot com 2010-08-13 22:30
---
OK thanks, is the code I attached here OK? I already submitted this to Atmel
also (#605725). Last time I submitted a bug to them this is the reply I got
back:
Note that avr-gcc and avr-libC are open-source pro
--- Comment #5 from eric dot weddington at atmel dot com 2010-08-13 01:14
---
Marking this bug as INVALID because the AVR Toolchain 3.0.0.207 is not an
officially released toolchain, and only in beta.
If you have any potential bugs, then please send to avr AT atmel DOT com, and
please
--- Comment #4 from darkdragon2000 at hotmail dot com 2010-08-12 23:56
---
Created an attachment (id=21473)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21473&action=view)
makefile
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45264
--- Comment #3 from darkdragon2000 at hotmail dot com 2010-08-12 23:56
---
Created an attachment (id=21472)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21472&action=view)
File which recreates the issue
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45264
--- Comment #2 from darkdragon2000 at hotmail dot com 2010-08-12 17:52
---
It's not a bug in the handler since when the interrupt fires at the point when
the stack pointer is invalid (right after 0x50c), the program counter gets
pushed onto the stack, which is an invalid location.
When
--- Comment #1 from rguenth at gcc dot gnu dot org 2010-08-12 15:15 ---
Why isn't this a bug in the interrupt handler?
What is "beta AVR toolchain 3.0.0.207" btw? We do not release such, so
maybe you should file a bug with the vendor releasing that?
--
http://gcc.gnu.org/bugzilla/
