octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: JIT threshold


From: Rik
Subject: Re: JIT threshold
Date: Tue, 09 Jul 2013 17:50:21 -0700

On 07/05/2013 08:56 PM, Michael D. Godfrey wrote:
> On 07/05/2013 05:28 PM, Rik wrote:
>>   I queried the mailing list in the last week or so and it seemed that
>> the desire was to keep JIT enabled by default whenever it was actually
>> built into Octave.
>>
>> --Rik
> I continue to agree with this.  From my experience it is ready for wider
> use.
> And, it is not likely that any remaining problems will be found unless a
> wider
> group of users begins using (and benefiting from) it.
7/9/13

Michael,

I liked a suggestion you made about making the threshold for JIT
acceleration customizable so I added a new function called jit_startcnt to
Octave
(http://hg.savannah.gnu.org/hgweb/octave/rev/e6ddaa65a777?revcount=120). 
Eventually if we collect enough parameters we can have a jit_options
function.  For the time being, it was much easier to just have a single
variable with a getter/setter routine.  The startcnt is the minimum number
of loop iterations required before JIT acceleration takes place.  I left
the default at the current value of 1000.

Cheers,
Rik
>
> Michael
>
>
>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]