public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tsaunders at mozilla dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/58575] New: gcc should compile firefox code faster. Date: Sun, 29 Sep 2013 21:19:00 -0000 [thread overview] Message-ID: <bug-58575-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58575 Bug ID: 58575 Summary: gcc should compile firefox code faster. Product: gcc Version: unknown Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: tsaunders at mozilla dot com CC: hubicka at ucw dot cz Its ceretainly possible given https://blog.mozilla.org/nnethercote/2013/09/12/bleg-for-a-new-machine-2/ (I'm not sure what versions njn is using but probably doesn't matter too much). I rofiled build a build of content/ in the firefox tree for a --enable-optimize --disable-debug build you can see the data I gathered at http://people.mozilla.org/~tsaunders/gcc-perf.data . The two things that came up high in profiles were C++ parsing stuff and memory allocation. I suppose there isn't too much to be done about the memory allocation issue in the short term, but I wonder if there's changes to the parser that would help at least some.
next reply other threads:[~2013-09-29 21:19 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-09-29 21:19 tsaunders at mozilla dot com [this message] 2013-10-02 8:31 ` [Bug c++/58575] " paolo.carlini at oracle dot com 2013-10-02 10:26 ` manu 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-58575-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).