public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "andi-gcc at firstfloor dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/63556] New: gcc should dedup string postfixes Date: Thu, 16 Oct 2014 08:53:00 -0000 [thread overview] Message-ID: <bug-63556-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63556 Bug ID: 63556 Summary: gcc should dedup string postfixes Product: gcc Version: 4.9.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: andi-gcc at firstfloor dot org With this code: extern void func(char *a, char *b); void f(void) { func("abc", "xabc"); func("abc", "abc"); } we get: .LC0: .string "xabc" .LC1: .string "abc" So the "abc"s get deduped. But it could also dedup the postfix by pointing "abc" to "xabc" + 1. This would save some space.
next reply other threads:[~2014-10-16 8:53 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-10-16 8:53 andi-gcc at firstfloor dot org [this message] 2014-10-16 8:54 ` [Bug middle-end/63556] " andi-gcc at firstfloor dot org 2014-10-16 9:07 ` rguenth at gcc dot gnu.org 2014-10-16 9:27 ` schwab@linux-m68k.org 2024-06-11 17:39 ` andi-gcc at firstfloor dot org 2024-06-13 9:23 ` xry111 at gcc dot gnu.org 2024-06-13 9:24 ` xry111 at gcc dot gnu.org 2024-06-13 9:40 ` jakub at gcc dot gnu.org 2024-06-13 13:43 ` andi-gcc at firstfloor dot org 2024-06-13 13:49 ` pinskia 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-63556-4@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).