Proceedings of the 41st Annual Design Automation Conference 2004
DOI: 10.1145/996566.996632
|View full text |Cite
|
Sign up to set email alerts
|

A general decomposition strategy for verifying register renaming

Abstract: This paper describes a strategy for verifying data-hazard correctness of out-of-order processors that implement register-renaming. We define a set of predicates to characterize register-renaming techniques and provide a set of model-checking obligations that are sufficient to guarantee that a register-renaming technique satisfies data-hazard correctness. We demonstrate how two register renaming techniques (retirement-register-file and dual-RAT) instantiate our predicates, and present model checking results for… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2005
2005
2010
2010

Publication Types

Select...
3

Relationship

0
3

Authors

Journals

citations
Cited by 3 publications
(1 citation statement)
references
References 19 publications
0
1
0
Order By: Relevance
“…For example, Levitt and Olukotun [1997] used formal verification for pipeline implementation to verify a design against itself. There have been efforts to verify formally almost all the features of a pipeline, for example, register renaming [Shehata et al 2004], speculative execution [Arons and Pnueli 2000;Sawada and Hunt 1998], out-of-order execution [Arons 2004;Damm and Pnuelli 1997], and Tomasulo's algorithm [Arons and Pnueli 1999;McMillan 1998]. However, these methods require detailed specifications of architectures as input to the verifier.…”
Section: Introductionmentioning
confidence: 99%
“…For example, Levitt and Olukotun [1997] used formal verification for pipeline implementation to verify a design against itself. There have been efforts to verify formally almost all the features of a pipeline, for example, register renaming [Shehata et al 2004], speculative execution [Arons and Pnueli 2000;Sawada and Hunt 1998], out-of-order execution [Arons 2004;Damm and Pnuelli 1997], and Tomasulo's algorithm [Arons and Pnueli 1999;McMillan 1998]. However, these methods require detailed specifications of architectures as input to the verifier.…”
Section: Introductionmentioning
confidence: 99%