Skip to content

Commit 5c90663

Browse files
committed
readme: update known issues
- Fixed typos. - Added a note regarding C declarations parser.
1 parent b31b1d3 commit 5c90663

File tree

1 file changed

+9
-5
lines changed

1 file changed

+9
-5
lines changed

README.md

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -80,10 +80,10 @@ limitations in LuaJIT and PUC Rio Lua:
8080
a part of the LuaJIT itself. Memory leaks are suppressed in
8181
AddressSanitizer with a function `__lsan_is_turned_off()` that
8282
disallows leak checking for the program it is linked into.
83-
1. In LuaJIT a function `lj_str_new()` may read past a buffer end
84-
(so-called "dirty" read) and that's ok. Suppressed in
83+
1. In LuaJIT, a function `lj_str_new()` may read past a buffer end
84+
(so-called "dirty" read), and that's ok. Suppressed in
8585
AddressSanitizer with `__attribute__((no_sanitize_address))`.
86-
1. In LuaJIT, bytecode input is unsafe, see [LuaJIT#847][LuaJIT#847]
86+
1. In LuaJIT, bytecode input is unsafe; see [LuaJIT#847][LuaJIT#847]
8787
and [LuaJIT FAQ][LuaJIT FAQ]. The string "mode" controls
8888
whether the chunk can be text or binary (that is, a precompiled
8989
chunk). It may be the string "b" (only binary chunks),
@@ -100,12 +100,16 @@ limitations in LuaJIT and PUC Rio Lua:
100100
violate basic assumptions about Lua code and therefore can
101101
compromise otherwise secure code. See [LuaJIT#1264][LuaJIT#1264]
102102
and [Lua 5.4 Reference Manual][refmanual54]. The `debug`
103-
functions is not a subject of testing and these functions are
103+
functions are not a subject of testing, and these functions are
104104
used carefully.
105-
1. In LuaJIT there are a number of places with undefined behavior
105+
1. In LuaJIT, there are a number of places with undefined behavior
106106
("nonnull-attribute", "signed-integer-overflow", "bounds").
107107
These problems remain unfixed and suppressed in
108108
UndefinedBehavior Sanitizer.
109+
1. In LuaJIT, there is a minimal C declaration parser, and it is not
110+
a validating C parser: "The parser ought to return correct
111+
results for properly formed C declarations, but it may accept
112+
some invalid declarations, too (and return nonsense)".
109113

110114
[LuaJIT#847]: https://github.com/LuaJIT/LuaJIT/issues/847
111115
[LuaJIT#1264]: https://github.com/LuaJIT/LuaJIT/issues/1264

0 commit comments

Comments
 (0)