From: Robert Kavaler <kavaler@flashcom.net>
To: linuxppc-dev@lists.linuxppc.org
Subject: Why does the PPC kernel architecture not use the builtin
Date: Sat, 05 Feb 2000 18:38:38 -0800 [thread overview]
Message-ID: <389CDEAE.FC4EAEB1@flashcom.net> (raw)
functions such as memcpy? Are these broken? I notice that the user
level code uses the builtin, but the kernel specifies -fno-builtin.
This seems like a big hit to efficiency.
In the same vein, the code (.h) to do byte swapping has a comment that
the ppc byteswap instruction should not be used, so instead a less
effecient code sequence is used. This is supposed to be a problem with
a specific rev. of the compiler. Does anyone know if this has been
fixed in the newest gcc or egcs (soon to be merged) compilers?
Thank you,
Robert Kavaler
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2000-02-06 2:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=389CDEAE.FC4EAEB1@flashcom.net \
--to=kavaler@flashcom.net \
--cc=linuxppc-dev@lists.linuxppc.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).