From: "Kevin D. Kissell" <kevink@paralogos.com>
To: David Daney <ddaney@caviumnetworks.com>
Cc: Manuel Lauss <manuel.lauss@googlemail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Ralf Baechle <ralf@linux-mips.org>,
Shane McDonald <mcdonald.shane@gmail.com>,
linux-mips@linux-mips.org
Subject: Re: Unexpected behaviour when catching SIGFPE on FPU-less system
Date: Tue, 04 May 2010 14:23:48 -0700 [thread overview]
Message-ID: <4BE09064.8010001@paralogos.com> (raw)
In-Reply-To: <4BE07D13.6010105@caviumnetworks.com>
David Daney wrote:
> On 05/04/2010 12:30 PM, Manuel Lauss wrote:
>> On Tue, May 4, 2010 at 9:28 PM, Geert
>> Uytterhoeven<geert@linux-m68k.org> wrote:
>>> On Tue, May 4, 2010 at 20:44, Ralf Baechle<ralf@linux-mips.org> wrote:
>>>> Is it paranoia by any chance? Paranoia is available as single
>>>> files at:
>>>>
>>>> http://www.math.utah.edu/~beebe/software/ieee/paranoia.c
>>>> http://www.math.utah.edu/~beebe/software/ieee/paranoia.h
>>>
>>> You also need
>>>
>>> http://www.math.utah.edu/~beebe/software/ieee/args.h
>>>
>>> Ran fine on:
>>> - Toshiba RBTX4927 (with FPU :-)
>>> - Mikrotik RouterBOARD 150 (without FPU), using an older 2.6.x
>>> OpenWRT kernel
>>
>> and runs into an endless loop around line 806 when built with
>> a softfloat toolchain (gcc-4.4.3).
>>
>
> From the point of view of this specific problem, using a softfloat
> toolchain isn't what you want to do.
That's absolutely true. I would mention, however, that in ancient
times, I built and ran paranoia with a couple of different softfloat
libraries, and was able to make it work with them. If people care about
softfloat (and I think they should), this should probably be
investigated. Easy for me to say, though... ;o)
Regards,
Kevin K.
next prev parent reply other threads:[~2010-05-04 21:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 2:17 Unexpected behaviour when catching SIGFPE on FPU-less system Shane McDonald
2010-05-03 20:39 ` Kevin D. Kissell
2010-05-03 20:47 ` Kevin D. Kissell
[not found] ` <k2hb2b2f2321005031843l87f39f36h960153cae3ec5020@mail.gmail.com>
2010-05-04 2:04 ` Kevin D. Kissell
[not found] ` <n2pb2b2f2321005032049h56cd72ceh3ac7120c547b59c5@mail.gmail.com>
2010-05-04 4:35 ` Shane McDonald
2010-05-04 6:56 ` Shane McDonald
2010-05-04 7:13 ` Shane McDonald
2010-05-04 11:16 ` Kevin D. Kissell
2010-05-04 12:56 ` Shane McDonald
2010-05-04 16:13 ` Kevin D. Kissell
2010-05-04 18:44 ` Ralf Baechle
2010-05-04 18:58 ` Kevin D. Kissell
2010-05-04 19:28 ` Geert Uytterhoeven
2010-05-04 19:30 ` Manuel Lauss
2010-05-04 19:44 ` Geert Uytterhoeven
2010-05-04 20:01 ` David Daney
2010-05-04 21:23 ` Kevin D. Kissell [this message]
2010-05-04 18:55 ` Kevin D. Kissell
2010-05-04 21:52 ` Kevin D. Kissell
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=4BE09064.8010001@paralogos.com \
--to=kevink@paralogos.com \
--cc=ddaney@caviumnetworks.com \
--cc=geert@linux-m68k.org \
--cc=linux-mips@linux-mips.org \
--cc=manuel.lauss@googlemail.com \
--cc=mcdonald.shane@gmail.com \
--cc=ralf@linux-mips.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.