public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tfrancuz at mp dot pl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/43746] New: -fmerge-constants and -fmerge-all-constants don't work at AVR target Date: Tue, 13 Apr 2010 08:23:00 -0000 [thread overview] Message-ID: <bug-43746-19028@http.gcc.gnu.org/bugzilla/> (raw) -fmerge-all-constants and –fmerge-constants don’t work at AVR target. Example: const char text1[] PROGMEM=”Test”; const char text2[] PROGMEM=”Test”; will still produce duplicated “Test” string in generated code. -- Summary: -fmerge-constants and -fmerge-all-constants don't work at AVR target Product: gcc Version: 4.3.5 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: tfrancuz at mp dot pl http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43746
next reply other threads:[~2010-04-13 8:23 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-04-13 8:23 tfrancuz at mp dot pl [this message] 2010-04-13 8:31 ` [Bug c++/43746] " j at uriah dot heep dot sax dot de 2010-04-14 20:46 ` tfrancuz at mp dot pl 2010-09-20 19:53 ` [Bug target/43746] " 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-43746-19028@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).