lua/ltests.h, branch v5.4.9A mirror of https://github.com/lua/lua
https://git.lua4.win/lua/atom?h=v5.4.92022-04-25T17:42:51+00:00Bug: Wrong code generation in bitwise operations2022-04-25T17:42:51+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2022-04-25T17:42:51+00:00urn:sha1:c764ca71a639f5585b5f466bea25dc42b855a4b0Details (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.
Back to a stackless implementation2020-10-12T15:29:09+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2020-09-21T13:31:03+00:00urn:sha1:5d8ce05b3f6fad79e37ed21c1076e47a322472c6
A "with stack" implementation gains too little in performance to be
worth all the noise from C-stack overflows.
This commit is almost a sketch, to test performance. There are several
pending stuff:
- review control of C-stack overflow and error messages;
- what to do with setcstacklimit;
- review comments;
- review unroll of Lua calls.
Clearer handling of gray lists when entering generational mode2020-08-03T16:22:57+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2020-08-03T16:22:57+00:00urn:sha1:b9b554e0f68726b19274209ea6ce910b7e9f5fbf
When entering generational mode, all objects are old. So, the only
objects that need to be in a gray list are threads, which can be
assigned without barriers. Changes in anything else (e.g., weak
tables) will trigger barriers that, if needed, will add the object
to a gray list.
Function 'printobj' in 'ltests.c' made public2020-07-27T14:24:03+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2020-07-27T14:24:03+00:00urn:sha1:8c7c9ea06502b8caa5224bf74c90a8885dbe0d42
It helps to have this function available for debugging.
Macro LUAI_ASSERT eases turning assertions on2020-07-08T18:51:55+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2020-07-08T18:51:55+00:00urn:sha1:6f5bd5072dff07679c390eecfeaa9d20cc45a9efDetails2020-04-30T20:29:27+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2020-04-30T20:29:27+00:00urn:sha1:948fb628d9d7242acfe1c3fe1f099ef228e38ead
When in test mode (#include "tests.h"), force Lua to use its own
implementation of 'lua_strx2number' and 'lua_number2strx' to test them.
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.
Clearer distinction between types and tags2020-01-31T14:09:53+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2020-01-31T14:09:53+00:00urn:sha1:46c3587a6feb28e1ee4a32aabe463b0ecb9e8f5e
LUA_T* represents only types; tags (types + Variants) are represented
by LUA_V* constants.
Small changes around C-stack limit2019-06-26T16:26:36+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-06-26T16:26:36+00:00urn:sha1:8b7cfee26b71e66de2cef9f8db9d9e18f5439afd
- Better documentation in 'testes/cstack.lua' about using
'debug.setCstacklimit' to find a good limit.
- Constant LUAI_MAXCSTACK gets added CSTACKERR (extra stack for
error handling), so that it is compatible with the argument to
'debug.setCstacklimit'.