[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: |
Fri, 8 Feb 2013 23:34:27 -0500 |
On Fri, Feb 8, 2013 at 5:37 PM, Michael D. Godfrey wrote:
> It may make sense to put code in Octave initialization which checks the FPU
> state,
> and modifies it if necessary. This will prevent this problem from coming
> back again.
I'm not sure I follow you, can you explain?
The FPU state is reset for every new process, so there's no need to
check it or set it when Octave starts up, if that's what you mean. In
theory any library we link into Octave could set it to whatever value
it wants at any time. So far both Java and ATLAS do this and do not
reset it when they return control to Octave.
--
mike
- Re: yet another Java oddity, (continued)
- Re: yet another Java oddity, Mike Miller, 2013/02/07
- Re: yet another Java oddity, Michael Goffioul, 2013/02/07
- 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 <=
- Re: yet another Java oddity, Michael D. Godfrey, 2013/02/08
- Re: yet another Java oddity, Mike Miller, 2013/02/10
- 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