| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Fixed some minor issues from the feedback for 5.4-beta rc1.
|
| | |
|
| |
|
|
|
|
| |
When converging marks on ephemeron tables, change the direction the
tables are traversed at each iteration, to try to avoid bad-case
scenarios with linked lists of entries in a table.
|
| |
|
|
|
|
|
|
| |
Open upvalues are kept alive together with their corresponding
stack. This change makes a simpler and safer fix to the issue in
commit 440a5ee78c8, about upvalues in the list of open upvalues
being collected while others are being created. (That previous fix
may not be correct.)
|
| |
|
|
|
| |
It is simpler to signal a to-be-closed upvalue with a boolean flag,
instead of using a different tag.
|
| |
|
|
|
|
|
|
| |
- Several new comments in 'lmem.c'.
- Both 'luaM_growaux_' and 'luaM_shrinkvector_' use 'luaM_saferealloc_'
to check for errors. Moreover, the use of 'luaM_saferealloc_' makes
'luaM_shrinkvector_' try again if shrink fails (which can happen now).
- In 'checkSizes', save old debt only when needed.
|
| | |
|
| |
|
|
|
|
|
|
| |
Fixes the bug related in [1] (Lua can crash after raising an error
in a finalizer), following the lead in [2].
[1] http://lua-users.org/lists/lua-l/2019-06/msg00448.html
[2] http://lua-users.org/lists/lua-l/2019-06/msg00450.html
|
| |
|
|
|
| |
Several small changes from feedback on 5.4 alhpa rc1 (warnings,
typos in the manual, and the like)
|
| |
|
|
|
|
| |
The 'GCSenteratomic' is just an auxiliary state for transitioning
to 'GCSatomic'. All GC traversals should be done either on the
'GCSpropagate' state or the 'GCSatomic' state.
|
| |
|
|
|
| |
Non-function __gc metamethods are not ignored; if present, the
metamethod will be called even if it is not a function.
|
| |
|
|
|
|
|
|
| |
- The warning functions get an extra parameter that tells whether
message is to be continued (instead of using end-of-lines as a signal).
- The user data for the warning function is a regular value, instead
of a writable slot inside the Lua state.
|
| |
|
|
|
|
|
| |
After a major bad collection (one that collects too few objects),
next collection will be major again. In that case, avoid switching
back to generational mode (as it will have to switch again to
incremental to do next major collection).
|
| |
|
|
|
| |
Errors in finalizers (__gc metamethods) are never propagated.
Instead, they generate a warning.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.)
|
| |
|
|
|
|
|
| |
Still missing:
- handling of memory errors when creating upvalue (must run closing
method all the same)
- interaction with coroutines
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Start of the implementation of "scoped variables" or "to be closed"
variables, local variables whose '__close' (or themselves) are called
when they go out of scope. This commit implements the syntax, the
opcode, and the creation of the corresponding upvalue, but it still
does not call the finalizations when the variable goes out of scope
(the most important part).
Currently, the syntax is 'local scoped name = exp', but that will
probably change.
|
| |
|
|
|
| |
Improved the comments in file 'lgc.c' explaining the roles of "ages"
OLD0 and OLD1 in the generacional collector.
|
| |
|
|
|
|
|
|
|
| |
During generational collection, a userdatum must become gray and
go to a gray list after being traversed (like tables), so that
'correctgraylist' can handle it to its next stage.
This commit also added minimum tests for the generational collector,
including one that would detect this bug.
|
| |
|
|
|
|
|
|
| |
When Lua is building large long-duration structures, frequent small
minor collections just waste time. Trying to avoid this, the
collector will do a larger pause after a major collection when it
does not collect enough garbage (which is a hint that memory is
being used for long-lasting objects).
|
| |
|
|
| |
be used as a hint for '#t'
|
| |
|
|
| |
(so it does not work when inside a block)
|
| |
|
|
| |
(a common case)
|
| | |
|
| |
|
|
| |
(so that, in the future, tables can contain regular nil entries)
|
| |
|
|
| |
(just moving stuff around)
|
| | |
|
| | |
|
| |
|
|
|
| |
(cannot call finalizers in emergency collections +
should set everything before calling finalizers)
|
| | |
|
| | |
|
| |
|
|
| |
set it only when needed.
|
| |
|
|
|
| |
automatically raise an error), which allows fixing a bug when resizing
a table.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
(we may want to put extra info there in the future)
|
| |
|
|
|
|
| |
if the key is dead, it cannot be given to 'next'. Instead, we now
use a 'table' tag without the collectable bit, which makes it
a unique tag good enough to reserve space.
|
| |
|
|
| |
space with alignments
|
| | |
|
| |
|
|
|
|
| |
Some simplifications (not counting bytes, couting only slots visited;
no more 'gcfinnum'); more GC parameters; using vararg in 'lua_gc' to
set parameters in different GC modes
|
| |
|
|
| |
prototypes to have their caches visited again) + constant 'MAXMISS'
|
| |
|
|
| |
hits that fail too often
|
| |
|
|
| |
minor collection
|
| |
|
|
| |
of mode)
|
