public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "d.v.a at ngs dot ru" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/60936] New: Binary code bloat with std::string Date: Wed, 23 Apr 2014 11:10:00 -0000 [thread overview] Message-ID: <bug-60936-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60936 Bug ID: 60936 Summary: Binary code bloat with std::string Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: d.v.a at ngs dot ru Test program: #include<string> int hello() { std::string st("abc"); return st.length(); } Build: $ g++ -shared -fPIC -static-libgcc -static-libstdc++ -Wl,-s -o $@ $? Sizes of result: gcc-4_7-string.so: 171744 gcc-4_8-string.so: 185808 gcc-4_9-string.so: 635960
next reply other threads:[~2014-04-23 11:10 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-23 11:10 d.v.a at ngs dot ru [this message] 2014-04-23 12:12 ` [Bug libstdc++/60936] " d.v.a at ngs dot ru 2014-04-23 12:37 ` d.v.a at ngs dot ru 2014-07-17 10:00 ` [Bug libstdc++/60936] [4.9 Regression] " d.v.a at ngs dot ru 2014-07-19 9:57 ` redi at gcc dot gnu.org 2014-07-19 10:32 ` redi at gcc dot gnu.org 2014-11-19 13:27 ` rguenth at gcc dot gnu.org 2015-04-15 11:36 ` [Bug libstdc++/60936] [4.9/5 " d.v.a at ngs dot ru 2015-04-15 11:38 ` redi at gcc dot gnu.org 2015-04-15 11:40 ` redi at gcc dot gnu.org 2015-04-15 13:41 ` [Bug libstdc++/60936] [4.9/5/6 " d.v.a at ngs dot ru 2015-04-23 7:38 ` d.v.a at ngs dot ru 2015-05-20 8:44 ` meisenmann.lba@fh-salzburg.ac.at 2015-05-20 11:31 ` 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-60936-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).