From: "La Monte H.P. Yarroll" <piggy@timesys.com>
To: Dan Malek <dan@embeddededge.com>
Cc: Kumar Gala <kumar.gala@freescale.com>,
LKML <linux-kernel@vger.kernel.org>,
Greg Weeks <greg.weeks@timesys.com>,
LinuxPPC-dev Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: [BUG] PPC math-emu multiply problem
Date: Thu, 29 Jul 2004 15:47:25 -0400 [thread overview]
Message-ID: <4109544D.5000405@timesys.com> (raw)
In-Reply-To: <A46787F8-E194-11D8-B8DB-003065F9B7DC@embeddededge.com>
Dan Malek wrote:
>
> On Jul 29, 2004, at 10:06 AM, Kumar Gala wrote:
>
>>
>> On Jul 29, 2004, at 8:14 AM, Greg Weeks wrote:
>>
>>> I'm seeing what appears to be a bug in the ppc kernel trap math
>>> emulator. An extreme case for multiplies isn't working the way gcc
>>> soft-float or hardware floating point is.
>>
>
> I'm not surprised. I lifted this code from Sparc, glibc, and adapted
> it as best I could for PPC years ago for the 8xx. I was happy when
> it appeared to work for the general cases. :-)
Thanks for doing the initial work!
> Due to its overhead, I never expected it to be _the_ solution for
> processors that don't have floating point hardware. Recompiling
> the libraries with soft-float and using that option when compiling
> is the way to go.
Indeed, when using this board for real we generally recommend
exactly the same thing.
> Remember, don't mix soft-float compilation with libraries compiled
> with HW floating point, and trap emulations. They are not
> compatible and will return erroneous results.
Unfortunately, LSB does not provide a set of test binaries which
use the softfloat ABI, so in order to get an LSB-comformant distribution
on this CPU, we need to use floating point emulation. Interestingly,
this is the only LSB floating point test which fails.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell's sig
next prev parent reply other threads:[~2004-07-29 19:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-29 13:14 [BUG] PPC math-emu multiply problem Greg Weeks
2004-07-29 14:06 ` Kumar Gala
2004-07-29 14:26 ` Greg Weeks
2004-07-29 19:22 ` Dan Malek
2004-07-29 19:47 ` La Monte H.P. Yarroll [this message]
2004-07-30 14:45 ` Greg Weeks
2004-07-30 15:23 ` Greg Weeks
2004-08-09 16:56 ` Tom Rini
2004-08-09 17:42 ` Dan Malek
2004-08-09 22:18 ` La Monte H.P. Yarroll
2004-08-09 22:23 ` Tom Rini
2004-08-16 13:02 ` Greg Weeks
2004-08-16 14:48 ` Tom Rini
2004-08-16 18:28 ` Greg Weeks
2004-08-16 18:35 ` Tom Rini
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=4109544D.5000405@timesys.com \
--to=piggy@timesys.com \
--cc=dan@embeddededge.com \
--cc=greg.weeks@timesys.com \
--cc=kumar.gala@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.