Abstract

We present a two-part approach for verifying out-of-order execution. First, the complexity of out-of-order issue and scheduling is handled by creating an in-order abstraction of the out-of-order execution core. Second, incremental flushing addresses the complexity difficulties encountered by automated abstraction functions on very deep pipelines. We illustrate the techniques on a model of a simple out-of-order processor core.

Document type: Part of book or chapter of book

Full document

The PDF file did not load properly or your web browser does not support viewing PDF files. Download directly to your device: Download PDF document

Original document

The different versions of the original document can be found in:


DOIS: 10.21236/ada400401 10.1007/bfb0028737

Back to Top

Document information

Published on 01/01/1998

Volume 1998, 1998
DOI: 10.21236/ada400401
Licence: CC BY-NC-SA license

Document Score

0

Views 3
Recommendations 0

Share this document

claim authorship

Are you one of the authors of this document?