[Top][All Lists]

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

[Octave-bug-tracker] [bug #56425] Patch for the JIT

From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #56425] Patch for the JIT
Date: Tue, 9 Jul 2019 11:32:33 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0

Follow-up Comment #19, bug #56425 (project octave):

OK, maybe I don't understand well enough the basics of how the JIT compiler is
supposed to work, so let's try to fix that problem first...

I was thinking that the JIT compiler worked on functions, but now I see it
also works on loops, independent of function bodies.  For loops, it could use
the current scope and stack frame to see whether a variable has been flagged
as global or persistent.

If compiling a complete function, I'm not sure how that would work since at
the beginning of a function evaluation the status of variables (global or
persistent) is not known unless global and persistent are handled as
parse-time declarations instead of executable statements as they are now.  It
seems to me that to properly handle global and persistent with the JIT
compiler we will need additional support from the parser and a change in the
way that global and persistent declarations work.  Given recent changes in
Matlab diagnostics for global and persistent declarations, it appears Matlab
is also heading in that direction.


Reply to this item at:


  Message sent via Savannah

reply via email to

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