public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "optech_tr at yahoo dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/38057] New: BUG: AVR-GCC ATMega2561 wrong addressing (probably eicall). Date: Fri, 07 Nov 2008 23:06:00 -0000 [thread overview] Message-ID: <bug-38057-16923@http.gcc.gnu.org/bugzilla/> (raw) 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
next reply other threads:[~2008-11-07 23:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-11-07 23:06 optech_tr at yahoo dot com [this message] 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
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-38057-16923@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).