From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21896 invoked by alias); 29 Sep 2013 21:19:48 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 21844 invoked by uid 48); 29 Sep 2013 21:19:44 -0000 From: "tsaunders at mozilla dot com" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: tsaunders at mozilla dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-09/txt/msg02008.txt.bz2 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.