Proceedings of the Sixth International Workshop on Hardware/Software Codesign. (CODES/CASHE'98)
DOI: 10.1109/hsc.1998.666252
|View full text |Cite
|
Sign up to set email alerts
|

Memory size estimation for multimedia applications

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
24
0

Publication Types

Select...
5
2

Relationship

1
6

Authors

Journals

citations
Cited by 31 publications
(24 citation statements)
references
References 10 publications
0
24
0
Order By: Relevance
“…Note that in contrast to other works [4], [9], [11], [12], [18] that require the loop bounds to be known constants, we derive closed-form expressions for the minimum memory size as a function of the loop bounds and dependence vectors. We consider the cases where the dimension of the array accessed within the loop is the same as the nest level and where the dimensionality is less than the loop nesting level.…”
Section: Example 1(a)mentioning
confidence: 99%
See 2 more Smart Citations
“…Note that in contrast to other works [4], [9], [11], [12], [18] that require the loop bounds to be known constants, we derive closed-form expressions for the minimum memory size as a function of the loop bounds and dependence vectors. We consider the cases where the dimension of the array accessed within the loop is the same as the nest level and where the dimensionality is less than the loop nesting level.…”
Section: Example 1(a)mentioning
confidence: 99%
“…Some early approaches in high-level synthesis that dealt with minimum register allocation for scalars [8] can be extended to arrays by treating each array element as a separate scalar; such an approach is highly expensive. Researchers from IMEC [1], [4], [11], [12], Grun et al [9], and Zhao and Malik [18] present techniques that estimate the minimum amount of memory required. Of these [11], [12] allow the user to specify an arbitrary execution ordering, Balasa et al [1] ignores execution ordering, while the rest of the works assume a fixed sequential execution ordering.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…Grun et al use the data-dependency relations between the array references in the code to find the number of array elements produced or consumed by each assignment [11]. The storage requirement at the end of a loop equals the storage requirement at the beginning of the loop, plus the number of elements produced within the loop, minus the number of elements consumed within the loop.…”
mentioning
confidence: 99%
“…The typical assumption int A [7][4], B [9][5], C [11][6], D [13] [7] ; for ( i=0; i<=6; i++ ) // 1st loop nest for ( j=0; j<=3; j++ )…”
mentioning
confidence: 99%