A negative index into a global is silent in bounds.flan, which is measured. "Because a global has no left redzone" was the explanation put on it, and it does not survive the obvious test: declare another defvar in front of arr and arr[-1] is caught, landing in that global's right redzone. Underflow detection is a question about what the linker put in front of the object, not about the access. Corrected in test_sanitize, BUILT.md and NEXT.md. NEXT.md's entry also goes back to its stated size. It had grown to 78 lines saying what BUILT.md says in the same commit range -- the attribute, the -O0 decision, the bounds.flan table -- which is the half-build-log the file's own header warns about. What stays here is what is next: the UBSan gap as an undecided compiler question, the four daemon-path buffers the corpus never reaches, and Valgrind.
Description
Languages
OCaml
67.2%
Emacs Lisp
15.2%
C
10.4%
HTML
2.9%
Standard ML
2.8%
Other
1.5%