From fa83b7df5a0711bf5f4a5162cc33b0a4123a53c7 Mon Sep 17 00:00:00 2001 From: _ov4 Date: Thu, 22 Oct 2026 15:06:13 +0000 Subject: fix(arrays): reject inverted bounds and check array allocation Constant inverted bounds are a compile error and other bounds are checked at run time. Allocation sizes use overflow-checked arithmetic, and a NULL malloc (including the BYVAL copy) reports that the array is too large. Co-Authored-By: Claude Sonnet 5.5 --- AGENTS/SUBSYSTEMS/ARRAYS.md | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'AGENTS') diff --git a/AGENTS/SUBSYSTEMS/ARRAYS.md b/AGENTS/SUBSYSTEMS/ARRAYS.md index 188ff5b..cc104a5 100644 --- a/AGENTS/SUBSYSTEMS/ARRAYS.md +++ b/AGENTS/SUBSYSTEMS/ARRAYS.md @@ -10,6 +10,10 @@ parameter binding/arguments in `ArrayParameters.cc`, and output in `ArrayOutput. - A DECLAREd array is one malloc'd flat buffer (memset to zero), row-major, any rank, any bounds. +- Every dimension needs `upper >= lower`: constant bounds are a compile error, other + bounds a runtime error (`emitCheckedByteSize`). The byte size is computed with + `llvm.{ssub,umul}.with.overflow`; overflow or a NULL malloc (also the BYVAL copy) + reports `Array X is too large`. Arrays therefore always have at least one element. - Bounds and multipliers are *SSA values* cached in `ArrayMetadata`. - `ArrayTable` is scoped per function (`exchangeTable`, driven from CodeGen's `FunctionDefAST` branch, mirroring the Symbols discipline). -- cgit v1.3.1-4-g156e