lua/lcode.h, branch v5.4.9A mirror of https://github.com/lua/lua
https://git.lua4.win/lua/atom?h=v5.4.92023-05-22T17:47:54+00:00Several functions turned 'static'2023-05-22T17:47:54+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2023-05-22T17:47:54+00:00urn:sha1:9be74ccc214eb6f4d9d0b9496fd973542c7377d9
Several functions that were already being used only inside their
own file have been declared as 'static'.
Details2020-02-27T15:59:22+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2020-02-27T15:59:22+00:00urn:sha1:6eb53b752617fae9e1329bfe2cfecdcbb593c398
Several details in code (e.g., moving a variable to the most inner
scope that encloses its uses), comments, parameter names, extra tests.
Simplification in the call to 'constfolding'2019-09-11T13:20:10+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-09-11T13:20:10+00:00urn:sha1:40d8832ee05096f9aea8eb54d1cdccf2646aecd0New kind of expression VKSTR2019-07-17T17:26:56+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-07-17T17:26:56+00:00urn:sha1:d6af81084df569bc8e3bd0949ad6fc0b40c8468d
String literal expressions have their own kind VKSTR, instead of the
generic VK. This allows strings to "cross" functions without entering
their constant tables (e.g., if they are used only by some nested
function).
Unification of size representation in OP_NEWTABLE and OP_SETLIST2019-07-15T17:59:35+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-07-15T17:59:35+00:00urn:sha1:758c1ef445ab27d89bace746111add04083a8e20
Opcodes OP_NEWTABLE and OP_SETLIST use the same representation to
store the size of the array part of a table. This new representation
can go up to 2^33 (8 + 25 bits).
OP_NEWTABLE keeps exact size of arrays2019-07-12T19:13:50+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-07-12T19:13:50+00:00urn:sha1:1fb4d539254b67e7e35ed698250c66d1edff0e08
OP_NEWTABLE is followed by an OP_EXTRAARG, so that it can keep
the exact size of the array part of the table to be created.
(Functions 'luaO_int2fb'/'luaO_fb2int' were removed.)
First implementation of constant propagation2019-07-12T14:38:42+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-07-12T14:38:42+00:00urn:sha1:f6aab3ec1f111cd8d968bdcb7ca800e93b819d24
Local constant variables initialized with compile-time constants
are optimized away from the code.
New implementation for constants2019-07-09T13:43:17+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-07-09T13:43:17+00:00urn:sha1:54f7b46c1e8a0188e1649046a3a72522f2d769f4
VLOCAL expressions keep a reference to their corresponding 'Vardesc',
and 'Upvaldesc' (for upvalues) has a field 'ro' (read-only). So, it is
easier to check whether a variable is read-only. The decoupling in
VLOCAL between 'vidx' ('Vardesc' index) and 'sidx' (stack index)
should also help the forthcoming implementation of compile-time
constant propagation.
First take on constant propagation2019-07-01T15:42:31+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-07-01T15:42:31+00:00urn:sha1:8eca21c2e85625390a2a3b08c231e75e315980b0Big revamp in the implmentation of labels/gotos2018-10-29T17:26:48+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2018-10-29T17:26:48+00:00urn:sha1:a006514ea138a29b6031058d9002b48a572b5dd6
Added restriction that, when a label is created, there cannot be
another label with the same name visible. That allows backward goto's
to be resolved when they are read. Backward goto's get a close if
they jump out of the scope of some variable; labels get a close only
if previous goto to it jumps out of the scope of some upvalue.