Hi Charlie,
1. There is a problem with JRuby: starting from b136 of JDK7, ruby refuses to
compile benchmark when -Xcompile.invokedynamic=true:
$ bin/jruby -X+C -Xcompile.invokedynamic=true
bench/bench_fib_recursive.rb
RuntimeError: could not compile and compile mode is 'force':
1. You can pass -d to JRuby to get the debug output from the failure,
or -Xjit.logging.verbose=true. I can take a look at this as soon as I
can update to java.lang.invoke.
2. I can fix the package reference quickly, but I'm using Rémi's
backport/mock which is still on java.dyn. I can't commit chan
On 04/06/2011 05:17 PM, Charles Oliver Nutter wrote:
> 1. You can pass -d to JRuby to get the debug output from the failure,
> or -Xjit.logging.verbose=true. I can take a look at this as soon as I
> can update to java.lang.invoke.
>
> 2. I can fix the package reference quickly, but I'm using Rémi's
On Wed, Apr 6, 2011 at 10:36 AM, Rémi Forax wrote:
> On 04/06/2011 05:17 PM, Charles Oliver Nutter wrote:
>> 2. I can fix the package reference quickly, but I'm using Rémi's
>> backport/mock which is still on java.dyn. I can't commit changes to
>> JRuby master that won't build on Java 6 and below,
On 04/06/2011 05:36 PM, Rémi Forax wrote:
> On 04/06/2011 05:17 PM, Charles Oliver Nutter wrote:
>> 1. You can pass -d to JRuby to get the debug output from the failure,
>> or -Xjit.logging.verbose=true. I can take a look at this as soon as I
>> can update to java.lang.invoke.
>>
>> 2. I can fix th
On 04/06/2011 06:06 PM, Charles Oliver Nutter wrote:
> On Wed, Apr 6, 2011 at 10:36 AM, Rémi Forax wrote:
>> On 04/06/2011 05:17 PM, Charles Oliver Nutter wrote:
>>> 2. I can fix the package reference quickly, but I'm using Rémi's
>>> backport/mock which is still on java.dyn. I can't commit change
On Wed, Apr 6, 2011 at 11:17 AM, Rémi Forax wrote:
> you can still run using the old linkage API (for 2 or 3 builds)
> using -XX:+allowTransitionalJSR292
Ok, I'll do that for now. I assume Linkage is still in the mock?
>>
>> What's the golden path forward at this point? Is indy solidified
>> eno
On Wed, Apr 6, 2011 at 11:22 AM, Charles Oliver Nutter
wrote:
> Ok, I'll do that for now. I assume Linkage is still in the mock?
Linkage does not appear to be in the mock, either under java.dyn or
java.lang.invoke.
- Charlie
___
mlvm-dev mailing list
m
On Wed, Apr 6, 2011 at 11:24 AM, Charles Oliver Nutter
wrote:
> On Wed, Apr 6, 2011 at 11:22 AM, Charles Oliver Nutter
> wrote:
>> Ok, I'll do that for now. I assume Linkage is still in the mock?
>
> Linkage does not appear to be in the mock, either under java.dyn or
> java.lang.invoke.
And the
On 04/06/2011 06:24 PM, Charles Oliver Nutter wrote:
> On Wed, Apr 6, 2011 at 11:22 AM, Charles Oliver Nutter
> wrote:
>> Ok, I'll do that for now. I assume Linkage is still in the mock?
> Linkage does not appear to be in the mock, either under java.dyn or
> java.lang.invoke.
>
> - Charlie
Yes,
On 04/06/2011 06:35 PM, Charles Oliver Nutter wrote:
> On Wed, Apr 6, 2011 at 11:24 AM, Charles Oliver Nutter
> wrote:
>> On Wed, Apr 6, 2011 at 11:22 AM, Charles Oliver Nutter
>> wrote:
>>> Ok, I'll do that for now. I assume Linkage is still in the mock?
>> Linkage does not appear to be in the
On Apr 6, 2011, at 9:35 AM, Charles Oliver Nutter wrote:
> And the flag does not seem to work either :(
>
> [apt] Warning: The flag +AllowTransitionalJSR292 has been EOL'd as of
> 7.0 and will be ignored
There might be ways you could combine a previous build with an even older
meth.jar (contain
Ok, running off jsr292-mock 1.6 and a prerelease build of ASM 4.0
(thanks Rémi for your help) I have pushed an updated branch that's all
java.lang.invoke, new bootstrap style, and properly compiling and
loading code.
https://github.com/jruby/jruby/tree/indy_update
The compile failure was because
In reading John's blog I saw a mention about changing dropArguments,
perhaps providing a simpler version?
I would like that.
In my code dropArguments is used to drop all but the first argument before
a bind and test for the
test branch of guardWtihTest. Mine is a special case where all of the
On 04/06/2011 08:52 PM, Mark Roos wrote:
In reading John's blog I saw a mention about changing dropArguments,
perhaps providing a simpler version?
I would like that.
In my code dropArguments is used to drop all but the first argument
before a bind and test for the
test branch of guardWtihTest
On Apr 6, 2011, at 3:10 PM, Rémi Forax wrote:
> You can also use the dropArguments that takes a List and use
> Arrays.asList() followed by subList().
If the desired MethodType is available, you can also use
MethodType.parameterList to get a List of the parameters (at O(1) likely
allocation cost
16 matches
Mail list logo