Re: Indy crash

2011-06-17 Thread Rémi Forax
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

Re: Indy crash

2011-06-16 Thread Rémi Forax
On 06/16/2011 08:23 PM, Charles Oliver Nutter wrote: On Wed, Jun 15, 2011 at 4:58 PM, Rémi Foraxfo...@univ-mlv.fr wrote: On 06/15/2011 09:55 PM, Charles Oliver Nutter wrote: On Wed, Jun 15, 2011 at 2:42 PM, Rémi Foraxfo...@univ-mlv.frwrote: You can use invokeWithArguments instead of

Re: Indy crash

2011-06-16 Thread Charles Oliver Nutter
On Thu, Jun 16, 2011 at 3:16 PM, Rémi Forax fo...@univ-mlv.fr 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

Re: Indy crash

2011-06-15 Thread Tom Rodriguez
I get the following message when I try to run it: InvokeDynamicSupport.java:468:in `invocationFallback': java.lang.invoke.WrongMethodTypeException:

Re: Indy crash

2011-06-15 Thread Charles Oliver Nutter
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,

Re: Indy crash

2011-06-15 Thread Jim Laskey
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

Auto Reply: Re: Indy crash

2011-06-15 Thread vladimir . x . ivanov
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

Re: Indy crash

2011-06-15 Thread Christian Thalinger
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

Re: Indy crash

2011-06-15 Thread Charles Oliver Nutter
On Wed, Jun 15, 2011 at 2:18 PM, Charles Oliver Nutter head...@headius.com 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

Re: Indy crash

2011-06-15 Thread Charles Oliver Nutter
On Wed, Jun 15, 2011 at 10:32 AM, Tom Rodriguez tom.rodrig...@oracle.com wrote: I get the following message when I try to run it: InvokeDynamicSupport.java:468:in `invocationFallback': java.lang.invoke.WrongMethodTypeException:

Re: Indy crash

2011-06-15 Thread Charles Oliver Nutter
On Wed, Jun 15, 2011 at 2:27 PM, Charles Oliver Nutter head...@headius.com 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

Re: Indy crash

2011-06-15 Thread Rémi Forax
On 06/15/2011 09:27 PM, Charles Oliver Nutter wrote: On Wed, Jun 15, 2011 at 10:32 AM, Tom Rodriguez tom.rodrig...@oracle.com wrote: I get the following message when I try to run it: InvokeDynamicSupport.java:468:in `invocationFallback': java.lang.invoke.WrongMethodTypeException:

Re: Indy crash

2011-06-15 Thread Charles Oliver Nutter
On Wed, Jun 15, 2011 at 2:42 PM, Rémi Forax fo...@univ-mlv.fr 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

Re: Indy crash

2011-06-15 Thread Charles Oliver Nutter
On Wed, Jun 15, 2011 at 2:59 PM, Tom Rodriguez tom.rodrig...@oracle.com 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

Re: Indy crash

2011-06-15 Thread Tom Rodriguez
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 repo to make

Re: Indy crash

2011-06-15 Thread Tom Rodriguez
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

Indy crash

2011-06-14 Thread Charles Oliver Nutter
I got this crash running a benchmark with indy stuff enabled (only the default stuff in JRuby master). Disabling use of invokedynamic fixes it. Build is based on MLVM a few days old. If it looks like something that might be fixed, I can pull a more recent trunk OpenJDK. ~/projects/jruby ➔ jruby

Re: Indy crash

2011-06-14 Thread Charles Oliver Nutter
On Tue, Jun 14, 2011 at 10:14 PM, John Rose john.r.r...@oracle.com 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

Re: Indy crash

2011-06-14 Thread Charles Oliver Nutter
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 head...@headius.com wrote: On Tue, Jun 14, 2011 at 10:14 PM, John Rose john.r.r...@oracle.com wrote: This looks like