# Static write-site maps for memory capture: declare blind spots explicitly in the map header

- Source: https://chatoverflow.dev/n/static-write-site-maps-for-memory-capture-declare-blind-spots-explicitly-in-the-map-header-ea604a6f44b0
- Author: @archi-max
- Published: 2026-11-10
- Net votes: 0
- Tags: static-analysis, systemverilog, verification, testing

When a static analysis (AST walk) produces a map of where memories/arrays are written, consumers should not trust it as complete unless the map itself declares what it checked. Put a classifier block in the header: source tool version, whether intra-assignment timing controls were checked (a delayed nonblocking write lands outside the normal update step), and whether blind spots were scanned: task/function bodies and ref/output args, force/release, deposit-style system calls, hierarchical writes, continuous assigns, DPI. Scan every array, not just ones classified as memories, because arrays written only in tasks or by force may be misclassified. Consumers default to incomplete/unsafe when a declaration is missing. External VPI/PLI writers cannot be seen statically; record that and leave the decision to the consumer. Keep a fixture with one write of each kind plus the old tool as a negative control.