[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MIT-Scheme-devel] floating-point environment
From: |
Joe Marshall |
Subject: |
Re: [MIT-Scheme-devel] floating-point environment |
Date: |
Fri, 8 Oct 2010 09:15:17 -0700 |
>> Date: Thu, 7 Oct 2010 12:38:59 -0700
>> From: address@hidden (Matt Birkholz)
>>
>> Can a Scheme-side cache of the machine configuration avoid much of the
>> cost of thread switching by punting fesetenv() when switching to a
>> thread with the same expectation of the floating-point environment?
I'd be surprised if thread-switching were frequent enough that this would make
a difference.
On Thu, Oct 7, 2010 at 8:57 PM, Taylor R Campbell <address@hidden> wrote:
> What I have in mind is for every
> continuation invocation -- including those used to switch threads --
> to do fesetenv.
I assume you mean every *non-local* continuation.
> It may also be necessary to frob the floating-point
> environment in the thread timer interrupt handler. This all may turn
> out to be prohibitively expensive -- I'll find out when I implement
> and measure it.
--
~jrm
- [MIT-Scheme-devel] floating-point environment, Taylor R Campbell, 2010/10/06
- Re: [MIT-Scheme-devel] floating-point environment, Taylor R Campbell, 2010/10/07
- [MIT-Scheme-devel] floating-point environment, Matt Birkholz, 2010/10/07
- Re: [MIT-Scheme-devel] floating-point environment, Taylor R Campbell, 2010/10/07
- Re: [MIT-Scheme-devel] floating-point environment, Matt Birkholz, 2010/10/13
- Re: [MIT-Scheme-devel] floating-point environment, Taylor R Campbell, 2010/10/13
- Re: [MIT-Scheme-devel] floating-point environment, Matt Birkholz, 2010/10/14
- Re: [MIT-Scheme-devel] floating-point environment, Taylor R Campbell, 2010/10/15
- Re: [MIT-Scheme-devel] floating-point environment, Matt Birkholz, 2010/10/22
- Re: [MIT-Scheme-devel] floating-point environment, Taylor R Campbell, 2010/10/23