From: Cort Dougan <cort@fsmlabs•com>
To: Chris Wedgwood <cw@f00f•org>
Cc: Paul Mackerras <paulus@samba•org>,
Eugene Surovegin <ebs@ebshome•net>,
brian.auld@adic•com, linuxppc-embedded@lists•linuxppc.org
Subject: Re: PowerMac vs. Intel for PowerPC Development Host
Date: Thu, 20 Feb 2003 12:43:18 -0700 [thread overview]
Message-ID: <20030220194318.GC9782@host109.fsmlabs.com> (raw)
In-Reply-To: <20030220054534.GA24107@f00f.org>
Ah, if that's the case, another data point. The 2.8 GHz dual P4, with
hyperthreading on (very important) and make -j 8 gives me a 1m 45s _devel
tree build for the ebony. If the cache is warm it's faster but that's
with a cold buffer cache.
} 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 19:43 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
2003-02-20 19:43 ` Cort Dougan [this message]
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=20030220194318.GC9782@host109.fsmlabs.com \
--to=cort@fsmlabs$(echo .)com \
--cc=brian.auld@adic$(echo .)com \
--cc=cw@f00f$(echo .)org \
--cc=ebs@ebshome$(echo .)net \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
--cc=paulus@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox