public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/34734] attribute((progmem)) not handled properly in C++ for AVRs Date: Thu, 30 Jun 2011 13:30:00 -0000 [thread overview] Message-ID: <bug-34734-4-0KZlgBYlut@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-34734-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34734 --- Comment #7 from Georg-Johann Lay <gjl at gcc dot gnu.org> 2011-06-30 13:28:46 UTC --- Author: gjl Date: Thu Jun 30 13:28:43 2011 New Revision: 175705 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=175705 Log: PR target/34734 Backport from mainline * config/avr/avr.c (avr_handle_progmem_attribute): Move warning about uninitialized data attributed 'progmem' from here... (avr_encode_section_info): ...to this new function. (TARGET_ENCODE_SECTION_INFO): New define. (avr_section_type_flags): For data in ".progmem.data", remove section flag SECTION_WRITE. Modified: branches/gcc-4_6-branch/gcc/ChangeLog branches/gcc-4_6-branch/gcc/config/avr/avr.c
next prev parent reply other threads:[~2011-06-30 13:30 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-34734-4@http.gcc.gnu.org/bugzilla/> 2011-02-06 12:24 ` Kicer86 at gmail dot com 2011-06-29 7:58 ` gjl at gcc dot gnu.org 2011-06-30 13:30 ` gjl at gcc dot gnu.org [this message] 2011-06-30 13:41 ` gjl at gcc dot gnu.org 2011-06-30 13:48 ` gjl at gcc dot gnu.org 2011-07-04 12:51 ` gjl at gcc dot gnu.org 2014-02-16 10:03 ` [Bug target/34734] [4.2/4.3/4.5/4.6 Regression][avr] attribute((progmem)) not handled properly in C++ jackie.rosen at hushmail dot com 2008-01-11 2:28 [Bug c++/34734] New: attribute((progmem)) not handled properly in C++ for AVRs markuslampert at yahoo dot com 2008-02-02 8:12 ` [Bug target/34734] " ilgb at livius dot net 2008-03-07 21:00 ` hsteinhaus at gmx dot de 2009-08-07 19:16 ` eric dot weddington at atmel dot com 2009-08-07 19:18 ` eric dot weddington at atmel dot com 2010-06-09 9:16 ` mschulze at ivs dot cs dot ovgu dot de
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-34734-4-0KZlgBYlut@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).