public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "artemeas at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/49764] [gcc-avr] Compiling for Arduino is not working Date: Sat, 16 Jul 2011 19:06:00 -0000 [thread overview] Message-ID: <bug-49764-4-eA87Gjdbe0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49764-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49764 --- Comment #7 from _artem_ <artemeas at gmail dot com> 2011-07-16 19:05:46 UTC --- I don't understand what you want from me. I read that "How to report, what we need and what we don't" SO? What info you want from me in addition to the text I posted in the bug report? I don't know "the complete command line that triggers the bug;" because I don't know how to compile that code outside of IDE. I upgraded gcc (GCC not gcc-avr) from 4.6.0 to 4.6.1 couple of days ago, gcc-avr was still 4.6.0. I was able to compile for arduino (ATmega328P-PU). I installed 4.6.1 of gcc-avr and I'm unable to compile for ATmega328 from IDE. I downgraded ONLY gcc-avr to 4.6.0 result: IDE compiles code. upgraded to 4.6.1 again and I can't compile again. You would ONLY need 3 minutes to download and to run that IDE on both versions of gcc-avr. and You would know what's the reason is. I don't what is causing this errors, the only thing that was changed on my machine is the GCC-AVR version, from 4.6.0->4.6.1 lines 66-.. that are in the error: 66 extern const uint16_t PROGMEM port_to_mode_PGM[]; 67 extern const uint16_t PROGMEM port_to_input_PGM[]; 68 extern const uint16_t PROGMEM port_to_output_PGM[]; 69 70 extern const uint8_t PROGMEM digital_pin_to_port_PGM[]; 71 // extern const uint8_t PROGMEM digital_pin_to_bit_PGM[]; 72 extern const uint8_t PROGMEM digital_pin_to_bit_mask_PGM[]; 73 extern const uint8_t PROGMEM digital_pin_to_timer_PGM[]; on gcc-avr 4.6.0 I get no errors on that code, on gcc-avr 4.6.1 I get error listed in the first message. "variable 'port_to_mode_PGM' must be const in order to be put into read-only" produced from this: extern const uint16_t PROGMEM port_to_mode_PGM[]; was there something changed in gcc-avr that would give such an error?
next prev parent reply other threads:[~2011-07-16 19:06 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-07-16 16:44 [Bug target/49764] New: " artemeas at gmail dot com 2011-07-16 16:47 ` [Bug target/49764] " artemeas at gmail dot com 2011-07-16 17:26 ` redi at gcc dot gnu.org 2011-07-16 17:34 ` redi at gcc dot gnu.org 2011-07-16 17:57 ` artemeas at gmail dot com 2011-07-16 18:10 ` redi at gcc dot gnu.org 2011-07-16 18:13 ` redi at gcc dot gnu.org 2011-07-16 19:06 ` artemeas at gmail dot com [this message] 2011-07-16 19:36 ` redi at gcc dot gnu.org 2011-07-16 19:55 ` artemeas at gmail dot com 2011-07-16 20:26 ` redi at gcc dot gnu.org 2011-07-17 0:30 ` artemeas at gmail dot com 2011-07-17 9:55 ` redi at gcc dot gnu.org 2011-07-17 9:57 ` redi at gcc dot gnu.org 2011-07-17 10:03 ` redi at gcc dot gnu.org 2011-07-23 18:42 ` gjl at gcc dot gnu.org 2011-07-23 19:27 ` gjl at gcc dot gnu.org 2011-07-23 19:30 ` gjl at gcc dot gnu.org 2011-07-25 10:24 ` [Bug target/49764] [avr-g++] Rejects attribute progmem gjl at gcc dot gnu.org 2011-07-26 19:34 ` artemeas at gmail dot com 2011-07-27 1:19 ` redi at gcc dot gnu.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-49764-4-eA87Gjdbe0@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).