From: Kumar Gala <galak@kernel.crashing.org>
To: Kevin Hao <haokexin@gmail.com>
Cc: Scott Wood <scottwood@freescale.com>,
linuxppc <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 1/2] powerpc: split the math emulation into two parts
Date: Mon, 22 Jul 2013 09:36:05 -0500 [thread overview]
Message-ID: <4E35EEC3-D4D8-4C03-B22E-5574584539AE@kernel.crashing.org> (raw)
In-Reply-To: <1373975836-11928-2-git-send-email-haokexin@gmail.com>
On Jul 16, 2013, at 6:57 AM, Kevin Hao wrote:
> For some SoC (such as the FSL BookE) even though there does have
> a hardware FPU, but not all floating point instructions are
> implemented. Unfortunately some versions of gcc do use these
> unimplemented instructions. Then we have to enable the math emulation
> to workaround this issue. It seems a little redundant to have the
> support to emulate all the floating point instructions in this case.
> So split the math emulation into two parts. One is for the SoC which
> doesn't have FPU at all and the other for the SoC which does have the
> hardware FPU and only need some special floating point instructions to
> be emulated.
>=20
> Signed-off-by: Kevin Hao <haokexin@gmail.com>
> ---
> arch/powerpc/Kconfig | 20 ++++++++++++++++++++
> arch/powerpc/math-emu/Makefile | 24 ++++++++++++------------
> arch/powerpc/math-emu/math.c | 20 ++++++++++++++------
> 3 files changed, 46 insertions(+), 18 deletions(-)
why make the split, what harm is there in just turning on the full =
emulation code to handle the unimplemented cases?
who says what some other implementation doesn't need something that you =
have in CONFIG_MATH_EMULATION_FULL?
Is the kernel code size really an issue?
- k=
next prev parent reply other threads:[~2013-07-22 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 11:57 [PATCH 0/2] powerpc: split the match emulation into two parts Kevin Hao
2013-07-16 11:57 ` [PATCH 1/2] powerpc: split the math " Kevin Hao
2013-07-22 14:36 ` Kumar Gala [this message]
2013-07-22 17:25 ` Scott Wood
2013-07-16 11:57 ` [PATCH 2/2] powerpc/mpc85xx: only emulate the unimplemented FP instructions on corenet64 Kevin Hao
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=4E35EEC3-D4D8-4C03-B22E-5574584539AE@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=haokexin@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@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