From: Dan Malek <dan@mvista.com>
To: frowand@mvista.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: program exception emulates mfspr PVR
Date: Thu, 15 Feb 2001 17:52:37 -0500 [thread overview]
Message-ID: <3A8C5DB5.2CE9D3C@mvista.com> (raw)
In-Reply-To: 3A8C5A95.9A94F914@mvista.com
Frank Rowand wrote:
> And why add this extra cruft?
Perhaps you should ask the people that requested it, probably one
or two doors down from your office..........
It was added so programs (actually libraries) executing prior to
any of the /proc stuff set up (like init) could detect the processor
type and install (or avoid) a variety of instructions unique to
that processor. Cache line information, availability of floating point,
Altivec, unique silicon errata workarounds, etc. could be incorporated
into the library, reducing the requirement to have uniquely compiled
libraries for all of the processor variants. This has been discussed
for ages on a variety of mailing lists, and emulating the 'mfspr PVR',
which is hardly cruft compared to some of the other stuff that exists,
was the easiest and least intrusive method.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-02-15 22:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-15 22:06 calling giveup_altivec on machine with no altivec!? Troy Benjegerdes
2001-02-15 22:20 ` Frank Rowand
2001-02-15 22:33 ` Troy Benjegerdes
2001-02-15 22:47 ` Frank Rowand
2001-02-15 22:39 ` program exception emulates mfspr PVR Frank Rowand
2001-02-15 22:52 ` Dan Malek [this message]
2001-02-15 23:41 ` Mark Hatle
2001-02-15 22:57 ` calling giveup_altivec on machine with no altivec!? Dan Malek
2001-02-18 2:41 ` Troy Benjegerdes
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=3A8C5DB5.2CE9D3C@mvista.com \
--to=dan@mvista.com \
--cc=frowand@mvista.com \
--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).