Be careful with don't cares

  • Authors:
  • Daniel Brand;Reinaldo A. Bergamaschi;Leon Stok

  • Affiliations:
  • IBM Research Division, T.J. Watson Research Center, Yorktown Heights, N.Y.;IBM Research Division, T.J. Watson Research Center, Yorktown Heights, N.Y.;IBM Research Division, T.J. Watson Research Center, Yorktown Heights, N.Y.

  • Venue:
  • ICCAD '95 Proceedings of the 1995 IEEE/ACM international conference on Computer-aided design
  • Year:
  • 1995

Quantified Score

Hi-index 0.00

Visualization

Abstract

Abstract: It is commonly expected that any correct implementation can replace its specification inside a larger design without violating the correctness of the whole design. This property (called replaceability) is automatically satisfied in the absence of don't cares because "correctness" by definition implies that specification and implementation compute the identical function. However don't cares allow an implementation to compute a different function, and thus make it difficult to ensure replaceability. Whether this problem occurs depends on the exact meaning of "don't care" and the associated definition of "correctness". We will consider three meanings of "don't care" and for each give conditions under which correct implementations may replace their specifications.