On Mar 24, 2011, at 4:06 PM, Christian Thalinger wrote:
I reran JRuby tests today and noticed a couple of problems. One I'd like an
opinion on is test/test_crazy_blocks. It fails with invokedynamic and I'm
not sure if either JRuby or the JDK has a bug.
Charlie, do you have an idea?
Hi,
On Sat, Mar 26, 2011 at 11:04 PM, Y. Srinivas Ramakrishna
y.s.ramakris...@oracle.com wrote:
You might try switching on heap verification to see if it finds any
issues:-
-XX:+UnlockDiagnosticVMOptions -XX:+VerifyBeforeGC -XX:+VerifyafterGC
I don't think it found any issues, below is
On Mar 28, 2011, at 7:15 PM, shanka@gmail.com wrote:
The complete hs_err log file is pasted here:
http://pylonshq.com/pasties/4ce99d93fbe70ee1347df7fc100934d2
What else should I try?
-XX:+UseSerialGC. It seems my previous email didn't make it to the list.
--
OpenJDK b135 has JVM support for the new package name java.dyn.invoke, and
therefore the new API names can be used with a b135 JVM plus a suitable
-Xbootclasspath patch. In b136 or b137 the JDK changes will follow, so it will
work out of the box.
Here's my question: Does anybody care if we
On Mon, Mar 28, 2011 at 11:44 AM, Christian Thalinger
christian.thalin...@oracle.com wrote:
-XX:+UseSerialGC. It seems my previous email didn't make it to the list.
This worked. Well sort of. The JVM doesn't crash because of a GC issue now.
However, this uncovered another issue. The JVM
I say get rid of vestigial packages / names as soon as possible.
Thanks,
Ben
On Mon, Mar 28, 2011 at 9:02 PM, John Rose john.r.r...@oracle.com wrote:
OpenJDK b135 has JVM support for the new package name java.dyn.invoke, and
therefore the new API names can be used with a b135 JVM plus a
Nuke it from orbit. It's the only way to be sure.
On Mon, Mar 28, 2011 at 3:57 PM, Ben Evans
benjamin.john.ev...@gmail.com wrote:
I say get rid of vestigial packages / names as soon as possible.
Thanks,
Ben
On Mon, Mar 28, 2011 at 9:02 PM, John Rose john.r.r...@oracle.com wrote:
OpenJDK
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Totally agree. Let's just get rid of it as quickly as possible.
(what's the status on the BSD builds, btw?)
Cheers
On 2011-03-28 15.58, Charles Oliver Nutter wrote:
Nuke it from orbit. It's the only way to be sure.
On Mon, Mar 28, 2011 at 3:57
On Mon, Mar 28, 2011 at 2:56 PM, Y. Srinivas Ramakrishna
y.s.ramakris...@oracle.com wrote:
In that case, try the latest repo (b05 or b06); Tom recently fixed a race
that might
be affecting you when using one of the parallel collectors:-
You may have noticed that the JSR 292 API includes a conversion operator
(called MethodHandles.asInstance) to allow a method handles to interoperate
with single-method interfaces, such as Runnable. This is a small but (maybe)
useful subset of the SAM conversion which is being defined by
I think I'd use it if it were available.
On an unrelated sidenote, I totally read that as who needs assistance
On Mar 28, 2011, at 3:37 PM, John Rose wrote:
You may have noticed that the JSR 292 API includes a conversion operator
(called MethodHandles.asInstance) to allow a method handles to
I am ready to make the change myself, go for it.
Where will the anonymousClassLoader end up?
mark
From:
John Rose john.r.r...@oracle.com
To:
Da Vinci Machine Project mlvm-dev@openjdk.java.net
Date:
03/28/2011 01:03 PM
Subject:
the fate of java.dyn
Sent by:
mlvm-dev-boun...@openjdk.java.net
On Mar 28, 2011, at 4:14 PM, Mark Roos wrote:
Where will the anonymousClassLoader end up?
In sun.invoke.anon. (Was sun.dyn.anon.) -- John___
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
On Mar 28, 2011, at 4:11 PM, Attila Szegedi wrote:
I think I'd use it if it were available.
Also, can you say what you'd use it for, and/or what you'd do without it?
Thanks, -- John
___
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
On Mar 28, 2011, at 1:06 PM, Jim Laskey wrote:
java.dyn.invoke = java.lang.invoke
On 2011-03-28, at 5:02 PM, John Rose wrote:
OpenJDK b135 has JVM support for the new package name java.dyn.invoke...
D'oh! I'll take that as an indication we want to flush dyn from our symbol
tables
I find this a difficult question because I haven't had chance to
experiment enough with them for my application; multiple dispatch.
asInterface is potentially useful but I need to trial different
approaches, which is currently work in progress. Therefore my answer
is include asInterface if it is:
I don't think it would really matter if there was:
java.lang.Class.asSAMInstance(mh)
and
java.lang.invoke.MethodHandles.asInstance(mh, interface)
That did a similar thing, the Javadoc could just describe them as
alternative ways of doing the same or similar (perhaps the Class
version would
Sorry :) Busy busy busy. I'll try to have a look soon.
If you feel up to it, filing a bug at http://bugs.jruby.org would make
sure we don't forget about it, and would act as another ping.
- Charlie
On Mon, Mar 28, 2011 at 4:30 AM, Christian Thalinger
christian.thalin...@oracle.com wrote:
On
D'oh! I'll take that as an indication we want to flush dyn from our symbol
tables ASAP.
Yes, the new package name is java.lang.invoke.
-- John
On Mar 28, 2011, at 1:06 PM, Jim Laskey wrote:
java.dyn.invoke = java.lang.invoke
On 2011-03-28, at 5:02 PM, John Rose wrote:
OpenJDK b135 has
19 matches
Mail list logo
