Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 30 Jan 2008 14:18:23 -0800
From:      Marcel Moolenaar <xcllnt@mac.com>
To:        Rafal Jaworowski <raj@semihalf.com>
Cc:        yanegomi@gmail.com, perforce@FreeBSD.org, marcel@FreeBSD.org, "M. Warner Losh" <imp@bsdimp.com>, grehan@FreeBSD.org
Subject:   Re: PERFORCE change 133911 for review
Message-ID:  <C4B18265-CCE0-4C6C-BCB3-DB259B48D406@mac.com>
In-Reply-To: <47A0BE7A.1030307@semihalf.com>
References:  <200801230414.m0N4E4ng009323@repoman.freebsd.org> <4797C8E0.4070100@freebsd.org> <4798C436.6090904@gmail.com> <20080125.100006.-262784007.imp@bsdimp.com> <479A17AC.4070004@freebsd.org> <479A26CE.6020104@semihalf.com> <EA167362-268D-4F5E-805F-2CE2B7D0D5BE@mac.com> <47A0BE7A.1030307@semihalf.com>

next in thread | previous in thread | raw e-mail | index | archive | help

On Jan 30, 2008, at 10:14 AM, Rafal Jaworowski wrote:

>>> IIRC, almost any AIM binary I tried executing caused FP exceptions
>>> (actually,
>>> an illegal instrusction ;) on e500, even such that wouldn't be
>>> expected tu use
>>> FPU. I didn't investigate this at all, but maybe the compiler was
>>> using FPRs
>>> for optimizations or something of that sort, don't know, so the  
>>> frequency
>>> might not be that low in reality.
>>
>> We didn't see this at all. We typically only saw ntpdate
>> and top crap out, because they actually use FP. Most of
>> the binaries were fine without -softfloat.
>>
>> Note also that a stray FP status register initialization
>> operation in crtX can cause all processes to fail, even
>> if there's no FP in the process. Your problem may have
>> been caused by libc, crt or libgcc. In fact, we may have
>> seen it ourselves as well and fixed that place to get to
>> where we ended up without softfloat (i.e. only ntpdate,
>> top, etc capping out).
>
> Hm, yes, this could be it. Do you happen to recall the proximity of  
> those
> fixes/changes you have applied back then? It's nothing serious, I'm  
> just
> curious, maybe I'd give this another spin in free time (he, he).

I think it was libc. We eliminated fp{g|s}etmask and friends
from libc if I'm not mistaken.

> I also had a closer look at your import and it seems to me some  
> further work
> is required:

I know. I just imported it as-is. I need to glue it into the
FreeBSD sources.

-- 
Marcel Moolenaar
xcllnt@mac.com





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C4B18265-CCE0-4C6C-BCB3-DB259B48D406>