2003
DOI: 10.1145/950162.950168
|View full text |Cite
|
Sign up to set email alerts
|

Code size reduction technique and implementation for software-pipelined DSP applications

Abstract: Software pipelining technique is extensively used to exploit instruction-level parallelism of loops, but also significantly expands the code size. For embedded systems with very limited on-chip memory resources, code size becomes one of the most important optimization concerns. This paper presents the theoretical foundation of code size reduction for software-pipelined loops based on retiming concept. We propose a general Code-size REDuction technique (CRED) for various kinds of processors. Our CRED algorithms… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
26
0

Year Published

2005
2005
2008
2008

Publication Types

Select...
5
1
1

Relationship

2
5

Authors

Journals

citations
Cited by 27 publications
(26 citation statements)
references
References 16 publications
0
26
0
Order By: Relevance
“…The code size is increased by introducing the prologue and epilogue after performing retiming. This problem can be solved by the code size reduction technique such as in [35].…”
Section: The Retiming Techniquementioning
confidence: 99%
“…The code size is increased by introducing the prologue and epilogue after performing retiming. This problem can be solved by the code size reduction technique such as in [35].…”
Section: The Retiming Techniquementioning
confidence: 99%
“…Code size reduction can be generally applied to any processors with or without predicate registers, and achieves smaller code size. For the details, please refer to the work published in [25].…”
Section: ¢£ ( ' )mentioning
confidence: 99%
“…From the results of the first phase, a basic candidate solution set I b ={3,5,7,8} is obtained from the candidate loop body by reselectable instruction map table. The basic candidate solutions generate a set of solution space {φ, 3, 5, 7, 8, (3,5), (3,7), (3,8), (5,7), (5,8), (7,8), (3,5,7), (3,5,8), (3,7,8), (5,7,8), (3,5,7,8)}. But, the branch and bound procedure discards the element 3 and 8 by heuristically chosen lower bound ,which we used 0.5, because those elements does not contribute an optimum solution.…”
Section: Phase 2: Branch and Bound Solution Search Strategymentioning
confidence: 99%
“…By carefully applying the preprocessing to the mission critical loops with profiling, the overall code size increase can be moderated. In addition, we recognize a research on code size reduction technique for software-pipelined loops [7]. The reported solution is based on a novel retiming function to reduce prologue and epilogue code sections with predication.…”
Section: Descriptionmentioning
confidence: 99%