On Fri, Jun 17, 2011 at 1:33 PM, Rémi Forax wrote:
> Should be fixed now.
> could you try with jsr292-backport-1.7a.zip ?
All good. thank you!
___
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
On 06/17/2011 08:17 PM, Rémi Forax wrote:
> On 06/17/2011 08:15 PM, Charles Oliver Nutter wrote:
>> :(
>>
>> [apt]
>> /Users/headius/projects/jruby/src/org/jruby/runtime/invokedynamic/InvokeDynamicSupport.java:602:
>> cannot find symbol
>> [apt] symbol : method
>> invokeWithArgume
On 06/17/2011 08:15 PM, Charles Oliver Nutter wrote:
> :(
>
>[apt]
> /Users/headius/projects/jruby/src/org/jruby/runtime/invokedynamic/InvokeDynamicSupport.java:602:
> cannot find symbol
>[apt] symbol : method
> invokeWithArguments(org.jruby.runtime.ThreadContext,org.jruby.runtime
:(
[apt]
/Users/headius/projects/jruby/src/org/jruby/runtime/invokedynamic/InvokeDynamicSupport.java:602:
cannot find symbol
[apt] symbol : method
invokeWithArguments(org.jruby.runtime.ThreadContext,org.jruby.runtime.builtin.IRubyObject,org.jruby.runtime.builtin.IRubyObject,java.lang
On Fri, Jun 17, 2011 at 4:18 AM, Rémi Forax wrote:
> Latest backport (1.7) mock jar includes ClassValue and
> 'excludes' Mh.invoke/invokeExact.
Awesome.
- Charlie
___
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
http://mail.openjdk.java.net/mailman
On 06/17/2011 02:49 AM, Charles Oliver Nutter wrote:
> On Thu, Jun 16, 2011 at 3:16 PM, Rémi Forax wrote:
>> good idea.
> One more request while you're in there... a mock for ClassValue :)
Latest backport (1.7) mock jar includes ClassValue and
'excludes' Mh.invoke/invokeExact.
> - Charlie
Rémi
On Thu, Jun 16, 2011 at 3:16 PM, Rémi Forax wrote:
> good idea.
One more request while you're in there... a mock for ClassValue :)
- Charlie
___
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
On 06/16/2011 09:27 PM, Charles Oliver Nutter wrote:
> On Thu, Jun 16, 2011 at 1:30 PM, Rémi Forax wrote:
>> The other reasonable solution is to patch the jdk6 compiler
>> to raise an error if MH.invoke*() is used.
> Actually, since I'm compiling against your backport's mock jar,
> perhaps you cou
Looks good with updated build!
On Thu, Jun 16, 2011 at 1:24 PM, Charles Oliver Nutter
wrote:
> I'll rebuild and give it a shot today.
>
> On Thu, Jun 16, 2011 at 2:28 AM, John Rose wrote:
>> I have folded Tom's fix for your crasher into the mlvm patch queue. Please
>> give it a whirl. -- John
On Thu, Jun 16, 2011 at 1:30 PM, Rémi Forax wrote:
> The other reasonable solution is to patch the jdk6 compiler
> to raise an error if MH.invoke*() is used.
Actually, since I'm compiling against your backport's mock jar,
perhaps you could add a deprecated or other warning on the
signature-polymo
On 06/16/2011 08:23 PM, Charles Oliver Nutter wrote:
> On Wed, Jun 15, 2011 at 4:58 PM, Rémi Forax wrote:
>> On 06/15/2011 09:55 PM, Charles Oliver Nutter wrote:
>>> On Wed, Jun 15, 2011 at 2:42 PM, Rémi Foraxwrote:
You can use invokeWithArguments instead of invokeExact.
>>> Yes, that hel
I'll rebuild and give it a shot today.
On Thu, Jun 16, 2011 at 2:28 AM, John Rose wrote:
> I have folded Tom's fix for your crasher into the mlvm patch queue. Please
> give it a whirl. -- John
>
> On Jun 15, 2011, at 12:22 PM, Charles Oliver Nutter wrote:
>
>> On Wed, Jun 15, 2011 at 2:18 PM,
On Wed, Jun 15, 2011 at 4:58 PM, Rémi Forax wrote:
> On 06/15/2011 09:55 PM, Charles Oliver Nutter wrote:
>> On Wed, Jun 15, 2011 at 2:42 PM, Rémi Forax wrote:
>>> You can use invokeWithArguments instead of invokeExact.
>> Yes, that helps, but I was under the impression that invokeExact would
>>
On Jun 15, 2011, at 11:18 PM, Tom Rodriguez wrote:
>
> On Jun 15, 2011, at 11:47 AM, Christian Thalinger wrote:
>
>> On Jun 15, 2011, at 8:08 PM, Charles Oliver Nutter wrote:
>>> FWIW, I only get the crash on my MLVM build if I pass these flags to JVM:
>>>
>>> -XX:MaxInlineSize=150 -XX:InlineSma
I have folded Tom's fix for your crasher into the mlvm patch queue. Please
give it a whirl. -- John
On Jun 15, 2011, at 12:22 PM, Charles Oliver Nutter wrote:
> On Wed, Jun 15, 2011 at 2:18 PM, Charles Oliver Nutter
> wrote:
>> Confirmed with your build (which is not surprising, perhaps).
>
I've fixed the WMT throwing and now I'm getting a real message.
MethodHandle.java:-1:in `invokeExact':
java.lang.invoke.WrongMethodTypeException: (Z)Ljava/lang/invoke/MethodHandle;
cannot be called as (Z)Ljava/lang/Object;
from /never/tmp/indy-crasher/date/format.rb:121:in
`method__4$RU
On 06/15/2011 09:55 PM, Charles Oliver Nutter wrote:
> On Wed, Jun 15, 2011 at 2:42 PM, Rémi Forax wrote:
>> You can use invokeWithArguments instead of invokeExact.
> Yes, that helps, but I was under the impression that invokeExact would
> do a better job inlining at least the early phases of the
On Jun 15, 2011, at 11:47 AM, Christian Thalinger wrote:
> On Jun 15, 2011, at 8:08 PM, Charles Oliver Nutter wrote:
>> FWIW, I only get the crash on my MLVM build if I pass these flags to JVM:
>>
>> -XX:MaxInlineSize=150 -XX:InlineSmallCode=3000
>>
>> See README and use jruby.jar from this rep
On Wed, Jun 15, 2011 at 2:59 PM, Tom Rodriguez wrote:
> I built the first time with 6 and had very weird problems so I tried
> rebuilding with 7 though I'm not sure I did it right. I'll try rebuilding
> and make sure it's really using 7. Until I resolve that ignore the issues
> below that I r
On Jun 15, 2011, at 12:27 PM, Charles Oliver Nutter wrote:
> On Wed, Jun 15, 2011 at 10:32 AM, Tom Rodriguez
> wrote:
>> I get the following message when I try to run it:
>>
>> InvokeDynamicSupport.java:468:in `invocationFallback':
>> java.lang.invoke.WrongMethodTypeException:
>> (Lorg/jruby/
On Wed, Jun 15, 2011 at 2:42 PM, Rémi Forax wrote:
> You can use invokeWithArguments instead of invokeExact.
Yes, that helps, but I was under the impression that invokeExact would
do a better job inlining at least the early phases of the invocation
into the call site. That may ore may not matter
On 06/15/2011 09:27 PM, Charles Oliver Nutter wrote:
> On Wed, Jun 15, 2011 at 10:32 AM, Tom Rodriguez
> wrote:
>> I get the following message when I try to run it:
>>
>> InvokeDynamicSupport.java:468:in `invocationFallback':
>> java.lang.invoke.WrongMethodTypeException:
>> (Lorg/jruby/runtime/
On Wed, Jun 15, 2011 at 2:27 PM, Charles Oliver Nutter
wrote:
> Toss me a couple of the tests that fail. I have not attempted to run
> the full test suite lately because a native library we need in some
> tests does not load on a non-universal OpenJDK build on OS X.
FWIW, I'm trying this now on L
On Wed, Jun 15, 2011 at 10:32 AM, Tom Rodriguez
wrote:
> I get the following message when I try to run it:
>
> InvokeDynamicSupport.java:468:in `invocationFallback':
> java.lang.invoke.WrongMethodTypeException:
> (Lorg/jruby/runtime/ThreadContext;Lorg/jruby/runtime/builtin/IRubyObject;Lorg/jruby
On Wed, Jun 15, 2011 at 2:18 PM, Charles Oliver Nutter
wrote:
> Confirmed with your build (which is not surprising, perhaps).
I should be more specific...I confirmed I cannot produce either
crash/failure on the build you sent me on Linux x86_64. It so far only
exhibits on current/recent MLVM buil
On Wed, Jun 15, 2011 at 1:47 PM, Christian Thalinger
wrote:
> Indeed I get a crash on Solaris and Linux using JDK7 b145. But with a bundle
> containing the latest two fixes all looks good:
>
> $ /java/re/jdk/7/promoted/all/b145/binaries/solaris-x64/bin/java -showversion
> -d64 -XX:MaxInlineSize
On Jun 15, 2011, at 8:08 PM, Charles Oliver Nutter wrote:
> FWIW, I only get the crash on my MLVM build if I pass these flags to JVM:
>
> -XX:MaxInlineSize=150 -XX:InlineSmallCode=3000
>
> See README and use jruby.jar from this repo to make it easier:
>
> https://github.com/headius/indy-crasher
FYI, I'm on vacation till June, 28.
If you have HotSpot-related question, please, contact Leonid Mesnik
(leonid.mes...@oracle.com).
Best regards,
Vladimir Ivanov
___
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
http://mail.openjdk.java.net/mailman/
I ran into a similar problem. Running out of CodeCache. I found I only ran
into it when profiling. Removing inline configuration made the problem go away.
Java HotSpot(TM) Client VM warning: CodeCache is full. Compiler has been
disabled.
Java HotSpot(TM) Client VM warning: Try increasing the
FWIW, I only get the crash on my MLVM build if I pass these flags to JVM:
-XX:MaxInlineSize=150 -XX:InlineSmallCode=3000
See README and use jruby.jar from this repo to make it easier:
https://github.com/headius/indy-crasher
I'll try that x64 build in a moment.
On Wed, Jun 15, 2011 at 7:38 AM,
I get the following message when I try to run it:
InvokeDynamicSupport.java:468:in `invocationFallback':
java.lang.invoke.WrongMethodTypeException:
(Lorg/jruby/runtime/ThreadContext;Lorg/jruby/runtime/builtin/IRubyObject;Lorg/jruby/runtime/builtin/IRubyObject;Ljava/lang/String;Lorg/jruby/runtime
On Jun 15, 2011, at 6:09 AM, Charles Oliver Nutter wrote:
> Still crashing! See previous email for hs dumpfile, command-line, and
> script, with link to data in the script.
I can not reproduce this crash on either Linux nor Solaris. Here is a recent
Linux x64 product build:
http://cr.openjdk.ja
Still crashing! See previous email for hs dumpfile, command-line, and
script, with link to data in the script.
- Charlie
On Tue, Jun 14, 2011 at 10:46 PM, Charles Oliver Nutter
wrote:
> On Tue, Jun 14, 2011 at 10:14 PM, John Rose wrote:
>> This looks like a failure fixed very recently (6/12) by
On Tue, Jun 14, 2011 at 10:14 PM, John Rose wrote:
> This looks like a failure fixed very recently (6/12) by the final version of
> meth-exc-7047697.patch.
>
> Please let me know ASAP if the latest version of that patch *fails* to fix
> your crash!
Doing an updated build from MLVM, where 'hotsp
This looks like a failure fixed very recently (6/12) by the final version of
meth-exc-7047697.patch.
Please let me know ASAP if the latest version of that patch *fails* to fix your
crash!
-- John
On Jun 14, 2011, at 8:00 PM, Charles Oliver Nutter wrote:
> I got this crash running a benchmark
35 matches
Mail list logo
