From: Kumar Gala <galak@kernel.crashing.org>
To: Alan Modra <amodra@bigpond.net.au>,
Paul Mackerras <paulus@samba.org>,
Wienskoski Edmar-RA8797 <RA8797@freescale.com>,
Stewart Katherine-RA4863 <ra4863@freescale.com>,
"Joseph S. Myers" <joseph@codesourcery.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: "linuxppc-dev@ozlabs.org list" <linuxppc-dev@ozlabs.org>,
libc-alpha@sourceware.org
Subject: HWCAP for fsqrt vs PPC64
Date: Fri, 25 Jun 2010 09:51:42 -0500 [thread overview]
Message-ID: <A147B597-35D6-47A4-A2A2-33954C37E332@kernel.crashing.org> (raw)
Guys,
We seem to be using the PPC_FEATURE_64 HWCAP to imply fsqrt support. =
However, the new e5500 core from Freescale that is 64-bit does NOT =
implement fsqrt so this assumption is wrong:
sysdeps/powerpc/fpu/math_private.h
# if __WORDSIZE =3D=3D 64 || defined _ARCH_PWR4
# define __CPU_HAS_FSQRT 1
# else
# define __CPU_HAS_FSQRT ((GLRO(dl_hwcap) & PPC_FEATURE_64) !=3D 0)
# endif
Open to suggestions on how to fix this as its a kernel/libc interaction =
point.
- k=
reply other threads:[~2010-06-25 14:55 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=A147B597-35D6-47A4-A2A2-33954C37E332@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=RA8797@freescale.com \
--cc=amodra@bigpond.net.au \
--cc=benh@kernel.crashing.org \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=ra4863@freescale.com \
/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