[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: yet another Java oddity
From: |
Mike Miller |
Subject: |
Re: yet another Java oddity |
Date: |
Sun, 10 Feb 2013 00:27:48 -0500 |
On Fri, Feb 8, 2013 at 11:39 PM, Michael D. Godfrey
<address@hidden> wrote:
> On 02/08/2013 11:34 PM, Mike Miller wrote:
>>
>> So far both Java and ATLAS do this and do not
>> reset it when they return control to Octave.
>
> Then is it not true that Octave should reset the FPU
> state on return from any code that leaves the state
> set differently from what Octave expects?
Yes I think that's how we should address it.
--
mike
- Re: yet another Java oddity, (continued)
- Re: yet another Java oddity, John W. Eaton, 2013/02/07
- Re: yet another Java oddity, Daniel J Sebald, 2013/02/07
- Re: yet another Java oddity, Mike Miller, 2013/02/08
- Re: yet another Java oddity, Jordi GutiƩrrez Hermoso, 2013/02/08
- Re: yet another Java oddity, Daniel J Sebald, 2013/02/08
- Re: yet another Java oddity, Daniel J Sebald, 2013/02/08
- Re: yet another Java oddity, Michael D. Godfrey, 2013/02/08
- Re: yet another Java oddity, Daniel J Sebald, 2013/02/08
- Re: yet another Java oddity, Mike Miller, 2013/02/08
- Re: yet another Java oddity, Michael D. Godfrey, 2013/02/08
- Re: yet another Java oddity,
Mike Miller <=
- Re: yet another Java oddity, Mike Miller, 2013/02/08
- Re: yet another Java oddity, Mike Miller, 2013/02/20
- Re: yet another Java oddity, CdeMills, 2013/02/07