From: David Edelsohn <dje@watson.ibm.com>
To: Paul Mackerras <paulus@samba.org>
Cc: "Joern Nettingsmeier" <nettings@folkwang-hochschule.de>,
"Kári Davíðsson" <kd@flaga.is>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: Powerbook
Date: Fri, 03 May 2002 21:54:52 -0400 [thread overview]
Message-ID: <200205040154.VAA28992@makai.watson.ibm.com> (raw)
In-Reply-To: Message from Paul Mackerras <paulus@samba.org> of "Sat, 04 May 2002 08:56:01 +1000." <15571.5505.916224.351719@argo.ozlabs.ibm.com>
>>>>> Paul Mackerras writes:
Paul> No, if you're in for quick compilation, compile a kernel for i386
Paul> rather than a kernel for ppc, for some reason gcc is quicker at
Paul> producing x86 output than ppc output, i.e. the x86 compilation
Paul> involves less computation.
PowerPC GCC is multi-arched by default for both 32-bit and 64-bit,
so many values internally are computed as 64-bit "long long" quantities.
i386 does not default to x86_64, so it uses word-sized ints.
PowerPC GCC has many more registers to allocate and more
restricted operands for instructions.
GCC on RISC (e.g., PowerPC) runs the scheduler at two different
phases of the compilation. GCC on CISC (e.g., i386) runs the scheduler
only once.
Those are some of the differences I can think of off the top of my
head.
David
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-05-04 1:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-03 12:04 Powerbook Kári Davíðsson
2002-05-03 13:43 ` Powerbook Joern Nettingsmeier
2002-05-03 15:09 ` Powerbook Anton Blanchard
2002-05-03 22:56 ` Powerbook Paul Mackerras
2002-05-04 1:54 ` David Edelsohn [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-05 14:16 Powerbook Kári Davíðsson
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=200205040154.VAA28992@makai.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=kd@flaga.is \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=nettings@folkwang-hochschule.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).