lua/lopcodes.h, branch v5.5.1A mirror of https://github.com/lua/lua
https://git.lua4.win/lua/atom?h=v5.5.12026-05-28T18:10:17+00:00Cleaning 'luaP_isIT' and 'luaP_isOT'2026-05-28T18:10:17+00:00Roberto Iroberto@inf.puc-rio.br2026-05-28T18:10:17+00:00urn:sha1:0465c23b3ee214ea3a117ab9d69a83cf85e7a82f
- 'luaP_isOT' is only used for tests, so it is defined as a macro to avoid
wasting space with an unused function.
- 'luaP_isIT' must include OP_VARARGPREP.
Functions with vararg tables don't need hidden args.2025-11-28T18:12:51+00:00Roberto Iroberto@inf.puc-rio.br2025-11-28T18:12:51+00:00urn:sha1:a07f6a824197d7dc01c321599d3bc71936a2590e
Vararg functions with vararg tables don't use the arguments hidden in
the stack; therfore, it doesn't need to build/keep them.
New conceptual model for vararg2025-11-26T14:18:29+00:00Roberto Iroberto@inf.puc-rio.br2025-11-26T14:18:29+00:00urn:sha1:f33cc4ddec886ea499d7d41dd60cac5ddc5687db
Conceptually, all functions get their vararg arguments in a vararg
table. The storing of vararg arguments in the stack is always treated
as an optimization.
Details2025-11-24T14:39:46+00:00Roberto Iroberto@inf.puc-rio.br2025-11-24T14:39:46+00:00urn:sha1:d94f7ba3040eb06895d7305014e88157d3bfd1a1
Comments, capitalization in the manual, globals in test 'heady.lua'
Global initialization checks name conflict2025-11-08T14:43:42+00:00Roberto Iroberto@inf.puc-rio.br2025-11-08T14:43:42+00:00urn:sha1:e44f3a2ffc7ced5e75cca7657aaa60ef27da89aa
Initialization "global a = 10" raises an error if global 'a' is already
defined, that is, it has a non-nil value.
Optimization for vararg tables2025-09-24T21:33:08+00:00Roberto Iroberto@inf.puc-rio.br2025-09-24T21:33:08+00:00urn:sha1:25c54fe60e22d05cdfaa48c64372d354efa59547
A vararg table can be virtual. If the vararg table is used only as
a base in indexing expressions, the code does not need to create an
actual table for it. Instead, it compiles the indexing expressions
into direct accesses to the internal vararg data.
Vararg table2025-09-16T16:26:24+00:00Roberto Iroberto@inf.puc-rio.br2025-09-16T16:26:24+00:00urn:sha1:140b672e2ee2ac842661ece4b48e1a64f0cd11ea
Not yet optimized nor documented.
Keep the order left-right in shifts2025-08-20T17:31:07+00:00Roberto Iroberto@inf.puc-rio.br2025-08-20T17:31:07+00:00urn:sha1:88aa4049ad3e638571bfffcf5fd8b6a8e07c6aaf
Opcodes OP_SHLI-OP_SHRI and the cases for opcodes OP_SHL-OP_SHR were
out of order.
Bug: check for constructor overflow in [exp] fields2025-05-20T20:50:56+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-05-20T20:50:56+00:00urn:sha1:c15543b9afa31ab5dc564511ae11acd808405e8f
The check for constructor overflow was considering only fields with
explicit names, ignoring fields with syntax '[exp]=exp'.
Janitorial work on casts2025-05-08T18:18:57+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-05-08T18:18:57+00:00urn:sha1:7ade1557627cf3f09c23c892ee227b7386f28414