public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "eric.weddington at atmel dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/50733] avr-gcc 4.3.5 generates incorrect code when using PROGMEM macro Date: Thu, 01 Dec 2011 12:44:00 -0000 [thread overview] Message-ID: <bug-50733-4-9zTxpiCj3r@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50733-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50733 Eric Weddington <eric.weddington at atmel dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |eric.weddington at atmel | |dot com Resolution| |WONTFIX --- Comment #3 from Eric Weddington <eric.weddington at atmel dot com> 2011-12-01 12:43:35 UTC --- This issue should go away when address spaces are done for the avr target (in future 4.7). The PROGMEM macro equates to a GCC attribute for that variable to place that into the Flash (Program Memory). It is up to the user to know this and to use the related macros in avr-libc to correctly retrieve the data from Flash. The AVR is a Harvard architecture chip and until Address Spaces were added to GCC it didn't have a good way of knowing these address spaces and able to generate a warning. I'm marking this bug as WONTFIX, but I suggest that the bug reporter add their email address to the CC field of bug #49868 (address spaces on the avr).
prev parent reply other threads:[~2011-12-01 12:44 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-14 19:52 [Bug c/50733] New: " marcos_vc at coel dot com.br 2011-10-19 11:01 ` [Bug target/50733] " wek at host dot sk 2011-10-19 15:03 ` marcos_vc at coel dot com.br 2011-12-01 12:44 ` eric.weddington at atmel dot com [this message]
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-50733-4-9zTxpiCj3r@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).