lua/ltm.c, branch v5.4.9

Stack indices changed to union's

2022-10-29T15:06:37+00:00

That will allow to change pointers to offsets while reallocating the stack.

Broadening the use of branch hints

2021-02-24T14:14:44+00:00

More uses of macros 'likely'/'unlikely' (renamed to 'l_likely'/'l_unlikely'), both in range (extended to the libraries) and in scope (extended to hooks, stack growth).

Fixed bugs of stack reallocation x GC

2020-07-07T21:03:48+00:00

Macro 'checkstackGC' was doing a GC step after resizing the stack; the GC could shrink the stack and undo the resize. Moreover, macro 'checkstackp' also does a GC step, which could remove the preallocated CallInfo when calling a function. (Its name has been changed to 'checkstackGCp' to emphasize that it calls the GC.)

Clearer distinction between types and tags

2020-01-31T14:09:53+00:00

LUA_T* represents only types; tags (types + Variants) are represented by LUA_V* constants.

Comment about LUA_COMPAT_LT_LE moved to proper place

2019-12-10T16:50:20+00:00

Undo change in the handling of 'L->top' (commit b80077b8f3)

2019-08-29T15:52:37+00:00

With MMBIN instructions, there are fewer opcodes that need to update 'L->top', so that change does not seem to pay for the increased complexity.

First version of OP_MMBIN opcodes

2019-08-27T16:59:39+00:00

In arithmetic/bitwise operators, the call to metamethods is made in a separate opcode following the main one. (The main opcode skips this next one when the operation succeeds.) This change reduces slightly the size of the binary and the complexity of the arithmetic/bitwise opcodes. It also simplfies the treatment of errors and yeld/resume in these operations, as there are much fewer cases to consider. (Only OP_MMBIN/OP_MMBINI/OP_MMBINK, instead of all variants of all arithmetic/bitwise operators.)

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'.)

Details (typos in comments)

2019-07-05T18:03:15+00:00

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