updat ops validations
This commit is contained in:
@@ -32,6 +32,18 @@ schedule semantics, scheduling granularity, and available parallelism.
|
||||
An optimization is acceptable only when its static runtime proxies are equal or
|
||||
better.
|
||||
|
||||
## Asymptotic cost
|
||||
|
||||
For each new or materially changed compiler algorithm, identify the relevant
|
||||
input size and target linear or sublinear time and space. Avoid repeated full-IR
|
||||
walks, nested scans, and per-operation recomputation when indexing, caching, or
|
||||
a single traversal can express the same behavior.
|
||||
|
||||
When linear-or-better complexity is not possible, use the lowest justified
|
||||
complexity and report the actual time and space Big-O, the input variable, and
|
||||
why a lower bound is not practical. Include that cost in the final report; do
|
||||
not hide a superlinear path behind small current test sizes.
|
||||
|
||||
## Forbidden optimization trades
|
||||
|
||||
Do not:
|
||||
|
||||
Reference in New Issue
Block a user