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/44643] ice in c-typeck.c Date: Thu, 26 May 2011 12:54:00 -0000 [thread overview] Message-ID: <bug-44643-4-xaOprunIHI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-44643-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44643 --- Comment #12 from Georg-Johann Lay <gjl at gcc dot gnu.org> 2011-05-26 12:52:10 UTC --- Author: gjl Date: Thu May 26 12:52:03 2011 New Revision: 174281 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=174281 Log: PR target/44643 * config/avr/avr.c (avr_insert_attributes): Leave TREE_READONLY alone. Error if non-const data has attribute progmem. 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-05-26 12:53 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-44643-4@http.gcc.gnu.org/bugzilla/> 2011-03-31 9:12 ` lts-rudolph at gmx dot de 2011-04-14 8:38 ` gjl at gcc dot gnu.org 2011-04-14 15:11 ` gjl at gcc dot gnu.org 2011-04-14 15:31 ` gjl at gcc dot gnu.org 2011-05-09 17:13 ` eric.weddington at atmel dot com 2011-05-23 17:05 ` jsm28 at gcc dot gnu.org 2011-05-26 12:54 ` gjl at gcc dot gnu.org [this message] 2011-06-16 17:27 ` gjl at gcc dot gnu.org 2011-06-18 14:32 ` gjl at gcc dot gnu.org 2011-07-04 12:28 ` gjl at gcc dot gnu.org 2011-07-04 12:34 ` gjl at gcc dot gnu.org 2011-07-04 12:36 ` gjl at gcc dot gnu.org 2011-07-04 12:48 ` gjl at gcc dot gnu.org 2010-06-23 3:21 [Bug c/44643] New: " weasel at cs dot stanford dot edu 2010-06-23 11:07 ` [Bug target/44643] " jsm28 at gcc dot gnu dot org 2010-06-23 15:59 ` weasel at cs dot stanford dot edu 2010-06-23 16:35 ` jsm28 at gcc dot gnu dot org 2010-06-28 1:06 ` pinskia at gcc dot gnu dot org
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-44643-4-xaOprunIHI@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).