[jruby-dev] JRuby 1.3.0 JSR223-JRuby Engine

2009-07-23 Thread Asiri Rathnayake
Hi, I'm have ported JSR223-JRuby Engine to work with JRuby 1.3.0 version (few minor adjustments only). However when using this engine with JRuby 1.3.0 I get an annoying error log which says: Error, could not compile; pass -d or -J-Djruby.jit.logging.verbose=true for more details Following is

Re: [jruby-dev] JRuby 1.3.0 JSR223-JRuby Engine

2009-07-23 Thread Yoko Harada
Hi Asiri, On Thu, Jul 23, 2009 at 5:08 AM, Asiri Rathnayakeasiri.rathnay...@gmail.com wrote: Hi, I'm have ported JSR223-JRuby Engine to work with JRuby 1.3.0 version (few minor adjustments only). However when using this engine with JRuby 1.3.0 I get an annoying error log which says: Error,

Re: [jruby-dev] Compiler IR thoughts

2009-07-23 Thread Thomas E Enebo
On Wed, Jul 22, 2009 at 2:11 PM, Subramanya Sastrysss.li...@gmail.com wrote: Obviously the IR already captures whether a closure accesses its own variables or captured variables, right? Implicitly yes.  This information will become explicit after reaching defs / live variable analysis is

Re: [jruby-dev] Compiler IR thoughts

2009-07-23 Thread Subramanya Sastry
Consider this: o.m1(..) o.m2(..) Since type of o hasn't changed between the 2 calls, you can skip the method table load for the second call.Anyway, I need to understand the call protocol in greater detail to comment more. This is an interesting use-case for closures. If