rusefi
/
lua
mirror of https://github.com/rusefi/lua.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
5,043 Commits 7 Branches 49 Tags 12 MiB
Commit Graph

132 Commits

Author SHA1 Message Date
Roberto Ierusalimschy fdc25a1ebf New functions 'lua_resetthread' and 'coroutine.kill' 
New functions to reset/kill a thread/coroutine, mainly (only?) to
close any pending to-be-closed variable. ('lua_resetthread' also
allows a thread to be reused...)
 2018-12-13 13:07:53 -02:00
Roberto Ierusalimschy 6d04537ea6 A to-be-closed variable must have a closable value (or be nil) 
It is an error for a to-be-closed variable to have a non-closable
non-nil value when it is being closed. This situation does not seem to
be useful and often hints to an error. (Particularly in the C API, it is
easy to change a to-be-closed index by mistake.)
 2018-11-29 16:02:44 -02:00
Roberto Ierusalimschy e8c779736f Removed internal cache for closures 
The mechanism of "caching the last closure created for a prototype to
try to reuse it the next time a closure for that prototype is created"
was removed. There are several reasons:

- It is hard to find a natural example where this cache has a measurable
impact on performance.

- Programmers already perceive closure creation as something slow,
so they tend to avoid it inside hot paths. (Any case where the cache
could reuse a closure can be rewritten predefining the closure in some
variable and using that variable.)

- The implementation was somewhat complex, due to a bad interaction
with the generational collector. (Typically, new closures are new,
while prototypes are old. So, the cache breaks the invariant that
old objects should not point to new ones.)
 2018-11-01 13:21:00 -03:00
Roberto Ierusalimschy 41c800b352 Closing methods should not interfere with returning values 
A closing method cannot be called in its own stack slot, as there may
be returning values in the stack after that slot, and the call would
corrupt those values. Instead, the closing method must be copied to the
top of the stack to be called.

Moreover, even when a function returns no value, its return istruction
still has to have its position (which will set the stack top) after
the local variables, otherwise a closing method might corrupt another
not-yet-called closing method.
 2018-10-25 12:50:20 -03:00
Roberto Ierusalimschy 3c7dc52909 Handling of memory errors when creating to-be-closed upvalues 2018-10-18 16:15:09 -03:00
Roberto Ierusalimschy bd96330d03 First "complete" implementation of to-be-closed variables 
Still missing:
- handling of memory errors when creating upvalue (must run closing
method all the same)
- interaction with coroutines
 2018-10-17 10:44:42 -03:00
Roberto Ierusalimschy f99509581e Removed extra information from RCS keyword strings 
Version numbers and dates (mostly wrong) from RCS keyword strings
removed from all source files; only the file name are kept.
 2018-08-23 14:26:12 -03:00
Roberto Ierusalimschy f96497397a new type 'StackValue' for stack elements 
(we may want to put extra info there in the future)
 2017-06-29 12:06:44 -03:00
Roberto Ierusalimschy b42430fd3a 'lineinfo' in prototypes saved as differences instead of absolute 
values, so that the array can use bytes instead of ints, reducing
its size. (A new array 'abslineinfo' is used when line differences
do not fit in a byte.)
 2017-06-27 08:35:31 -03:00
Roberto Ierusalimschy be0d951be8 bug: cannot reuse a dying upvalue 2017-05-24 15:54:54 -03:00
Roberto Ierusalimschy 8634b2a011 added 'cachemiss' field to prototype to avoid wasting time checking 
hits that fail too often
 2017-04-30 17:43:26 -03:00
Roberto Ierusalimschy a3d36fe283 Upvalues collected like everything else (with mark-sweep) instead 
of reference count (simpler and better for generational mode)
 2017-04-11 15:41:09 -03:00
Roberto Ierusalimschy 2331e1beec small changes in 'luaC_upvalbarrier' 2017-04-06 10:08:56 -03:00
Roberto Ierusalimschy 28fdbcf393 added include for 'lprefix.h', for stuff that must be added before 
any other header file
 2014-11-02 17:19:04 -02:00
Roberto Ierusalimschy bdf566a8a3 `name' in comments changed to 'name' 2014-10-25 09:50:46 -02:00
Roberto Ierusalimschy 89b56e7d84 more precision between closure types ('LClosure' x 'CClosure') 2014-06-19 15:27:20 -03:00
Roberto Ierusalimschy 14929f5764 use appropriate macros to convert GCObject to specific types 2014-06-18 19:59:29 -03:00
Roberto Ierusalimschy d764cc5522 new list 'twups' to allow traversal of upvalues from dead threads 
(+ fixed some problems with cycles involving those upvalues)
 2014-02-18 10:39:37 -03:00
Roberto Ierusalimschy ffa96d988d field 'op' renamed to 'open' 2014-02-15 11:12:01 -02:00
Roberto Ierusalimschy 733c58595b no more local collection 2014-02-13 10:11:34 -02:00
Roberto Ierusalimschy 1150873447 'luaC_newobj' does not handle special cases; only special case 
now is threads, which do not use 'luaC_newobj' anymore.
 2013-09-11 09:26:14 -03:00
Roberto Ierusalimschy 90972ff136 LOCALBLACK changed to LOCALMARK and used also to control whether object 
is in 'localgc' list + luaC_newobj by default puts object in 'localgc'
list
 2013-08-27 17:04:00 -03:00
Roberto Ierusalimschy af35c7f398 upvalues collected by reference count 2013-08-27 15:53:35 -03:00
Roberto Ierusalimschy 742b7377d3 Lua closures go to local, too 2013-08-26 09:41:10 -03:00
Roberto Ierusalimschy 50955e27f5 C functions and strings now go to the local list; first version 
of the local collector
 2013-08-23 10:34:54 -03:00
Roberto Ierusalimschy 439d74e29f added 'local' bit (true => object is only refered by local variables) 2013-08-16 15:55:49 -03:00
Roberto Ierusalimschy 623e388bb4 double-linked list of all upvalues elliminated and changed to a 
traversal of all non-marked threads
 2013-08-07 09:18:11 -03:00
Roberto Ierusalimschy 677d90165f no more generational collection !!! 2013-08-05 13:58:28 -03:00
Roberto Ierusalimschy 86b39206d9 open upvalues cannot be old if thread is not old; when thread is old, 
their list is not traversed anymore, and therefore can contain dead
elements.
 2012-10-03 09:36:46 -03:00
Roberto Ierusalimschy 3cadc37f47 no more 'Proto' objects on the stack. Protos are anchored on outer 
Protos or on a Closure, which must be created before the Proto.
 2012-05-08 10:53:33 -03:00
Roberto Ierusalimschy fd22ccd6d0 object tag keeps variant bits too -> no need for 'isC' field in 
Closures + more strick typing for closure variants
 2012-01-20 20:05:50 -02:00
Roberto Ierusalimschy a71c5f6f53 typo in comments 2010-06-30 11:11:17 -03:00
Roberto Ierusalimschy 0d116c3ada unused '#include' removed 2010-06-10 18:27:09 -03:00
Roberto Ierusalimschy 575074fd85 Lua closures are cached for reuse 2010-06-04 10:25:10 -03:00
Roberto Ierusalimschy 1c1a98e872 corrected some places where an old object could end up in front 
of a new one + minimal documentation about this problem
 2010-05-10 15:23:45 -03:00
Roberto Ierusalimschy 23001d8607 nasty GC bug: upvalue must be turned white when not keeping invariant, 
but barrier was not being called when uv->v were already white.
 2010-04-29 18:43:36 -03:00
Roberto Ierusalimschy 5a7a0c72d8 'luaC_linkupval' embedded into call site 2010-04-29 14:34:35 -03:00
Roberto Ierusalimschy 064e406f67 no more fenvs! 2010-03-26 17:58:11 -03:00
Roberto Ierusalimschy 25c557ec63 first version of _ENV; no more global variables 2010-03-12 16:14:06 -03:00
Roberto Ierusalimschy 0bbdddc86b allocator function receives the tag of object being allocated in 'osize' 
when 'ptr' is NULL.
 2009-12-17 13:46:44 -02:00
Roberto Ierusalimschy 3a9ae612a4 macro 'ngcotouv' is the same as 'gco2uv', so it was removed 2009-12-11 11:39:34 -02:00
Roberto Ierusalimschy 3c4d970a7b comment typos 2009-11-26 09:39:20 -02:00
Roberto Ierusalimschy 0ac3d07ea6 first implementation of lexical environments 2009-09-30 12:38:37 -03:00
Roberto Ierusalimschy 5938212748 information about upvalues (where they come from) kept in Proto structure, 
instead of sequence of pseudo-opcodes after OP_CLOSURE
 2009-09-28 13:32:50 -03:00
Roberto Ierusalimschy c6b442bd36 'luaM_freearray' does not need array type as argument 2009-04-17 11:40:13 -03:00
Roberto Ierusalimschy 593bfc9668 should not manipulate NULL pointers (even without accessing them) 2007-02-07 15:48:52 -02:00
Roberto Ierusalimschy c505f341d6 small changes in casts 2005-12-22 14:19:56 -02:00
Roberto Ierusalimschy 1ab2b93462 debug information for last line of a function definition 2005-05-05 17:47:02 -03:00
Roberto Ierusalimschy 9832f6b186 small bug 2005-04-29 10:54:05 -03:00
Roberto Ierusalimschy 7d45a5f48f C functions and userdata also have environments 2005-02-18 10:40:02 -02:00