From: Chris Wedgwood <cw@f00f.org>
To: Paul Mackerras <paulus@samba.org>, Eugene Surovegin <ebs@ebshome.net>
Cc: brian.auld@adic.com, linuxppc-embedded@lists.linuxppc.org
Subject: Re: PowerMac vs. Intel for PowerPC Development Host
Date: Wed, 19 Feb 2003 21:45:34 -0800 [thread overview]
Message-ID: <20030220054534.GA24107@f00f.org> (raw)
In-Reply-To: <5.1.0.14.2.20030219210505.037b67e8@mail.ebshome.net> <15956.11756.925757.532452@argo.ozlabs.ibm.com>
On Thu, Feb 20, 2003 at 12:22:52PM +1100, Paul Mackerras wrote:
> As an actual data point: my measurements show that a dual 1GHz G4
> powermac is more than twice as fast at compiling PPC kernels as a
> 1.7GHz P4 (single cpu).
Wow... that's *much* better that I would have guessed. Is the
compiler the same for each?
> You can't fairly compare compiling a PPC kernel on a PPC box with
> compiling an x86 kernel on an x86 box. GCC does more work compiling
> for PPC than for x86.
I wasn't trying to compare fairly, mostly get the lowest possible
compile time.
On Wed, Feb 19, 2003 at 09:10:48PM -0800, Eugene Surovegin wrote:
> I tried to compile the _same_ PPC kernel for one of boards (440GP
> based).
> Cross compiling on PIII 755Mhz running SuSE - 16 min
> Cross compiling on G4 PowerBook 1Ghz running YDL - 6 min
I don't have a PPC host to reasonably compare with, but a 440GP kernel
(linuxppc_2_4_devel) for me builds in 3 minutes 29s (with gcc-2.95).
--cw
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-02-20 5:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 21:52 PowerMac vs. Intel for PowerPC Development Host brian.auld
2003-02-19 22:29 ` Mark Hatle
2003-02-19 22:29 ` Kenneth Johansson
2003-02-19 22:29 ` bob piatek
2003-02-19 22:44 ` Wolfgang Denk
2003-02-20 1:01 ` Chris Wedgwood
2003-02-20 1:22 ` Paul Mackerras
2003-02-20 5:10 ` Eugene Surovegin
2003-02-20 5:45 ` Chris Wedgwood [this message]
2003-02-20 19:43 ` Cort Dougan
2003-02-20 19:40 ` Cort Dougan
2003-02-20 8:22 ` Jaap-Jan Boor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030220054534.GA24107@f00f.org \
--to=cw@f00f.org \
--cc=brian.auld@adic.com \
--cc=ebs@ebshome.net \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=paulus@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.