public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/38057] New: BUG: AVR-GCC ATMega2561 wrong addressing (probably eicall).
@ 2008-11-07 23:06 optech_tr at yahoo dot com
2008-11-13 21:37 ` [Bug target/38057] [AVR] " eric dot weddington at atmel dot com
2009-03-23 16:43 ` eric dot weddington at atmel dot com
0 siblings, 2 replies; 3+ messages in thread
From: optech_tr at yahoo dot com @ 2008-11-07 23:06 UTC (permalink / raw)
To: gcc-bugs
I wrote a code for atmega2561. The code's memory usage in prog memory is almost
153000 bytes.
The problem is, code doesn't work properly. the mcu getting reset or something
like this... I think compiled
code calls wrong addresses in somewhere of the memory. When I comment some of
part of text messages in the memory, the total memory usage become 126000 bytes
and the code works good....
I had also had a problem with eicall in winavr. I had fixed it like this:
EIND = 1;
asm("ldi r30,0x00");
asm("ldi r31,0xf0");
asm("eicall");
I guess avr-gcc doesn't set "EIND = 1;" for atmega2561 while compiling.
So i cannot using the other part of mega2561 (nearly 128K) because of this
BUG.
Please somebody fix it, it is very urgent...
Thanks....
--
Summary: BUG: AVR-GCC ATMega2561 wrong addressing (probably
eicall).
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: blocker
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: optech_tr at yahoo dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38057
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-03-23 16:43 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-11-07 23:06 [Bug c/38057] New: BUG: AVR-GCC ATMega2561 wrong addressing (probably eicall) optech_tr at yahoo dot com
2008-11-13 21:37 ` [Bug target/38057] [AVR] " eric dot weddington at atmel dot com
2009-03-23 16:43 ` eric dot weddington at atmel dot com
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).