Changeset: b752110df530
Author:weijun
Date: 2009-03-27 11:05 +0800
URL: http://hg.openjdk.java.net/jdk7/tl/jdk/rev/b752110df530
6802846: jarsigner needs enhanced cert validation(options)
Reviewed-by: xuelei
! src/share/classes/sun/security/tools/JarSigner.java
! src/share/classes/s
Changeset: 4a685f3f3ba8
Author:dl
Date: 2009-03-26 17:39 -0700
URL: http://hg.openjdk.java.net/jdk7/tl/jdk/rev/4a685f3f3ba8
6822903: Reliability and documentation improvements for ReentrantReadWriteLock
Summary: Make firstReader a Thread, not a long
Reviewed-by: martin
! src/share/
Changeset: 5303aece2068
Author:dl
Date: 2009-03-26 11:59 -0700
URL: http://hg.openjdk.java.net/jdk7/tl/jdk/rev/5303aece2068
6801020: Concurrent Semaphore release may cause some require thread not signaled
Summary: Introduce PROPAGATE waitStatus
Reviewed-by: martin
!
src/share/clas
On Mar 26, 11:01am, thomas.rodrig...@sun.com (Tom Rodriguez) wrote:
-- Subject: Re: SIGFPE with FPE_FLTRES
| > I would just remove the trancendental c implementation. It is not
| > consistent
| > with the java one anyway on amd64:
|
| You've got that backwards. The C implementation is actually
I would just remove the trancendental c implementation. It is not
consistent
with the java one anyway on amd64:
You've got that backwards. The C implementation is actually the
correct result as far as the spec goes and it's what is used by
StrictMath.log. Math.log is allowed to produce l
As far as I can see, "old FP" instructions are still emitted for
example for the logarithm (see log10D_reg and logD_reg in x86_64.ad,
which use fldlg2, fldln2 and fyl2x). These instructions can interact
badly with code generated by the native C/C++ compiler.
I had such a problem a while ago under
On Mar 25, 4:28pm, thomas.rodrig...@sun.com (Tom Rodriguez) wrote:
-- Subject: Re: SIGFPE with FPE_FLTRES
| That's even more odd to me. x86_64 shouldn't be using the old FP
| instructions and the SSE based one don't produce an inexact traps as
| far as I can tell. Maybe they are still being
