This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gcc3.3 30% speedup in the past 2 weeks (MICO compilation)
- From: Gerard Beekmans <gerard at linuxfromscratch dot org>
- To: gcc at gcc dot gnu dot org
- Date: Mon, 3 Mar 2003 14:06:59 -0700
- Subject: Re: gcc3.3 30% speedup in the past 2 weeks (MICO compilation)
- Organization: Linux From Scratch
- References: <Pine.LNX.4.43.0302230055410.16269-100000@thinkpad.c0202001.roe.itnq.net> <200302230952.23525.gerard@linuxfromscratch.org> <200302232300.SAA08457@caip.rutgers.edu>
On February 23, 2003 04:00 pm, Kaveh R. Ghazi wrote:
> "before" compiler. With 512Mb, the "after" compiler should show
> roughly 65% and 65536K but I've seen it vary depending on how
> "accurately" the OS responds to physmem's queries.
Pretty much. I have 64% and 64221K
I'll send these emails on a per-package basis as it makes more sense. Work is
tying me up so instead of waiting a long time for everything in on email I'll
send the test results as I get them.
I completed tests on QT-3.2.1.
With the "before" compiler it takes 48 minutes
With the "after" compiler it takes 42 minutes
(With gcc-3.2.1 it takes about 60 minutes)
I tried linux-2.4.18 and 2.4.20 but both fail to compiled with the 3.3-CVS
version so I tried the 2.5.63 version. They are pretty much the same, the
"before" compiler is 30 seconds faster (5.5 minutes as opposed to 6 minutes)
on a default config (make defconfig && time make bzImage).
kdebase is due next and I'll start on the packages from the release criteria
application "integration tests" page.
--
Gerard Beekmans
www.linuxfromscratch.org
-*- If Linux doesn't have the solution, you have the wrong problem -*-