lua/testes/code.lua, branch v5.4.9A mirror of https://github.com/lua/lua
https://git.lua4.win/lua/atom?h=v5.4.92022-12-28T21:34:11+00:00Avoid excessive name pollution in test files2022-12-28T21:34:11+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2022-12-28T21:34:11+00:00urn:sha1:314745ed8438d1276c6c928d5f9d4be018dfadb6
Test files are more polite regarding the use of globals when locals
would do, and when globals are necessary deleting them after use.
Changes in cache for function constants2021-03-30T17:49:18+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2021-03-30T17:49:18+00:00urn:sha1:36de01d9885562444ae2e2a3e0b7e01b3fb8743b
In 'lcode.c', when adding constants to the list of constants of a
function, integers represent themselves in the cache and floats
with integral values get a small delta to avoid collision with
integers. (This change avoids creating artificial addresses; the old
implementation converted integers to pointers to index the cache.)
Details (do not affect regular code)2020-12-07T14:17:30+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2020-12-07T14:17:30+00:00urn:sha1:e2ea3b31c94bb3e1da27c233661cb2a16699c685
* Avoids multiple definitions of 'lua_assert' in test file.
* Smaller C-stack limit in test mode.
* Note in the manual about the use of false
* Extra test for constant reuse.
Removed optimization for «if ... then goto»2020-11-11T17:41:41+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2020-11-11T17:41:41+00:00urn:sha1:ab1aca94e83d2eff1605ea1854df023c814cef21
That optimization was too complex and caused some weird traces when
debugging. The more common case «if ... then break» was kept.
Changed internal representation of booleans2020-01-06T14:38:31+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2020-01-06T14:38:31+00:00urn:sha1:5ff408d2189c6c24fdf8908db4a31432bbdd6f15
Instead of an explicit value (field 'b'), true and false use different
tag variants. This avoids reading an extra field and results in more
direct code. (Most code that uses booleans needs to distinguish between
true and false anyway.)
Janitorial work2019-10-01T20:24:37+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-10-01T20:24:37+00:00urn:sha1:b2a580bdb1982e45bb37f95b78c2dafec6efa7a6
- Several details in 'lcode.c'
- A few more tests for code generation
- Bug in assert in 'lcode.c' ("=" x "==")
- Comments in 'lopcodes.h' and 'ltable.c'
Subtraction of small constant integers optimized with OP_ADDI2019-09-24T17:34:52+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-09-24T17:34:52+00:00urn:sha1:6ef366644f7c3c21cfb17434835edf4ebf970d6dRemoved arithmetic opcodes with immediate operand2019-09-10T16:20:03+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-09-10T16:20:03+00:00urn:sha1:91dad09f65984048ae43c8894d18acb785c7092b
The difference in performance between immediate operands and K operands
does not seem to justify all those extra opcodes. We only keep OP_ADDI,
due to its ubiquity and because the difference is a little more relevant.
(Later, OP_SUBI will be implemented by OP_ADDI, negating the constant.)
Use of 'MMBIN' opcodes extended to shift operators2019-08-28T12:58:03+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-08-28T12:58:03+00:00urn:sha1:46b84580d6d7890f4ba813f312e52514fffc38a7
Plus, this commit removes useless 'tm' parameters in 'op_*' macros.
First version of OP_MMBIN opcodes2019-08-27T16:59:39+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-08-27T16:59:39+00:00urn:sha1:df13f259487459f3a28d31d76c890aa6c2d061e0
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.)