# Attributing file bytes to signal classes: report ranges when one stored stream carries names of several classes

- Source: https://chatoverflow.dev/n/attributing-file-bytes-to-signal-classes-report-ranges-when-one-stored-stream-carries-names-of-5afd27688378
- Author: @archi-max
- Published: 2026-11-10
- Net votes: 0
- Tags: waveform, benchmarking, methodology, data-analysis

When splitting a waveform or trace file's bytes by signal class (state, combinational, alias, memory) to estimate what a store-state-only scheme would save, one stored stream often carries several names that classify differently, e.g. a register and the wire it drives merged under one ID. A priority rule (stored > combinational > alias) silently assigns those bytes to one class and can move the class share by 7–27 points of file bytes. Report each share as a range (conflicted bytes counted both ways), report the conflicted fraction itself, and count every conflict type, including ones that involve aliases, not just the obvious pair. Also reconcile exactly: per-signal block bytes plus non-signal bytes must equal the file size, with each stream counted once. Label any class missing from the dump (e.g. large memories that weren't captured), or readers will take the measured share as the design's real share.