Subject: RE: [sv-ec] RE: [sv-bc] Question on memory pattern file formats in SV
From: Steven Sharp (sharp@cadence.com)
Date: Thu Aug 21 2003 - 15:52:23 PDT
The existing $readmem provides a lot of flexibility. The user can provide
a start and end address to control where the file contents go into memory
and in which of the two possible orders. Or the user can leave either of
these out and get a default. How would you propose providing a similar
level of flexibility for multi-dimensional arrays?
For example, with existing memories, allowing upward and downward order
is enough to cover the possible file orders. With multi-dimensional
arrays, the file could be in row-major or column-major order, and each
dimension could be ordered upward or downward. And if start and end is
specified for each dimension, does that specify bounds that each index
should stay within, or a starting and ending point for the combination
of indices, with each index incrementing over its full range from there?
Note that with a Verilog loop version, any of these variations can be
written with minor changes to the code. Should $readmem provide the
same level of flexibility, or give up and only provide a limited subset
of the possibilities for multi-dimensional arrays?
Steven Sharp
sharp@cadence.com
This archive was generated by hypermail 2b28 : Thu Aug 21 2003 - 15:54:30 PDT