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.
