This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Faster compilation speed
- From: "David S. Miller" <davem at redhat dot com>
- To: dje at watson dot ibm dot com
- Cc: dberlin at dberlin dot org, dan at dberlin dot org, austern at apple dot com, gcc at gcc dot gnu dot org
- Date: Tue, 13 Aug 2002 16:35:38 -0700 (PDT)
- Subject: Re: Faster compilation speed
- References: <dberlin@dberlin.org><200208132258.SAA27554@makai.watson.ibm.com>
From: David Edelsohn <dje@watson.ibm.com>
Date: Tue, 13 Aug 2002 18:58:25 -0400
The problem isn't that the number is low at optimization.
Can you control when the performance counters start/stop monitoring?
If so, then you can figure out more precisely whether it is mostly
during:
1) Front end tree or tree->rtl conversion
2) rest_of_compilation() onward
3) Both #1 and #2 about evenly, because all of our core data
structures come out of GC the whole compiler has bad spatial
and temporal locality
My money is on #3 :-)