public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/46347] New: Profile-mode executables too large Date: Sun, 07 Nov 2010 15:48:00 -0000 [thread overview] Message-ID: <bug-46347-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46347 Summary: Profile-mode executables too large Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: libstdc++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: paolo.carlini@oracle.com I believe we should seriously investigate whether we can reduce the size of the profile-mode executables. Likely that means we have also to add exports, but the current status seems really pretty bad. Just as a trivial example, on mainline today (rev 166416), x86_64, -O2, we have, for #include <vector> int main() { std::vector<int> v(100); v.push_back(2); } the following sizes: normal-mode: 12184 debug-mode: 17370 profile-mode: 130345
next reply other threads:[~2010-11-07 15:48 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-07 15:48 paolo.carlini at oracle dot com [this message] 2010-11-11 23:14 ` [Bug libstdc++/46347] " rus at google dot com 2010-11-11 23:53 ` paolo.carlini at oracle dot com 2010-12-10 16:54 ` paolo.carlini at oracle 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-46347-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).