lua/testes/events.lua, branch v5.4.9

Bug: Issues with write barrier for __newindex

2026-07-13T18:55:36+00:00

In 'luaV_finishset', there is an update on a table that is a field on another table. If the first table is the same as the one with the field (e.g., after 't.__newindex = t'), the update can change the value on that field (if the field being updated is '__newindex' itself). After that, the barrier is called with the table stored in that field, which is not the correct table anymore.

Bug: Use after free in 'luaV_finishset'

2025-03-13T18:42:39+00:00

If a metatable is a weak table, its __newindex field could be collected by an emergency collection while being used in 'luaV_finishset'. (This bug has similarities with bug 5.3.2-1, fixed in commit a272fa66.)

Avoid excessive name pollution in test files

2022-12-28T21:34:11+00:00

Test files are more polite regarding the use of globals when locals would do, and when globals are necessary deleting them after use.

Free bit 7 of GC 'marked' field

2020-08-07T14:21:44+00:00

Tables were using this bit to indicate their array sizes were real ('isrealasize'), but this bit can be useful for tests. Instead, they can use bit 7 of their 'flag' field for that purpose. (There are only six fast-access metamethods.) This 'flag' field only exists in tables, so this use does not affect other types.

Details

2020-02-27T15:59:22+00:00

Several details in code (e.g., moving a variable to the most inner scope that encloses its uses), comments, parameter names, extra tests.

Comments (mosty typos)

2019-12-30T14:45:08+00:00

Change in the handling of 'L->top' when calling metamethods

2019-07-26T17:59:39+00:00

Instead of updating 'L->top' in every place that may call a metamethod, the metamethod functions themselves (luaT_trybinTM and luaT_callorderTM) correct the top. (When calling metamethods from the C API, however, the callers must preserve 'L->top'.)

Keep correct type for immediate operands in comparisons

2019-03-22T16:37:17+00:00

When calling metamethods for things like 'a < 3.0', which generates the opcode OP_LTI, the C register tells that the operand was converted to an integer, so that it can be corrected to float when calling a metamethod. This commit also includes some other stuff: - file 'onelua.c' added to the project - opcode OP_PREPVARARG renamed to OP_VARARGPREP - comparison opcodes rewritten through macros

Added opcodes for arithmetic with K operands

2018-11-23T14:23:45+00:00

Added opcodes for all seven arithmetic operators with K operands (that is, operands that are numbers in the array of constants of the function). They cover the cases of constant float operands (e.g., 'x + .0.0', 'x^0.5') and large integer operands (e.g., 'x % 10000').

Removed extra information from RCS keyword strings in tests

2018-10-22T18:20:07+00:00

Version numbers and dates (mostly wrong) from RCS keyword strings removed from all test files; only the file name are kept.