This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC 3.3, GCC 3.4
- From: Mike Stump <mstump at apple dot com>
- To: Karel Gardas <kgardas at objectsecurity dot com>
- Cc: GCC Mailing List <gcc at gcc dot gnu dot org>
- Date: Thu, 30 Jan 2003 15:31:02 -0800
- Subject: Re: GCC 3.3, GCC 3.4
On Thursday, January 30, 2003, at 02:56 PM, Karel Gardas wrote:
As a gcc user badly affected by slow c++ compilation
I'd recommend profiling the compiler during compilation of your
software, and publish the results. I think users should file bug
reports naming the routines at the top (say the top 10). Maintainers
can then know if a certain set of routines pops up time after time
after time, that those routines (or their callers) should be
investigated and fixed.
I really would like to see such patches somewhere. So my question is:
where
gcc-patches is where all patches should go.
and when they'll appear in some of gcc branches?
As soon as they are ready.
Or are they just available for download for 'brave' g++ user who can
give them a try?
Not all patches are ready for prime time. If you want to try them as
they go by, you can, though, it is more work than most people want.
One back from that, after you know where your compilation time goes,
you can watch for that routine in gcc-patches, and the word speedup...
and after it goes into the mainline, you can just cvs update the
software, and give it a spin.
Also, it is useful for mere users to watch compile time performance of
their code with compilers from cvs, say weekly, or daily if you have
the spare cycles, and to yell when it suddenly is 5%+ slower. Every
10% you stop, is a 10% speed increase that might not otherwise be there.