Skip Navigation

The Computer Journal 2002 45(1):27-36; doi:10.1093/comjnl/45.1.27
© 2002 by British Computer Society
This Article
Right arrow Full Text (PDF)
Right arrow Alert me when this article is cited
Right arrow Alert me if a correction is posted
Services
Right arrow Email this article to a friend
Right arrow Similar articles in this journal
Right arrow Similar articles in ISI Web of Science
Right arrow Alert me to new issues of the journal
Right arrow Add to My Personal Archive
Right arrow Download to citation manager
Right arrow Search for citing articles in:
ISI Web of Science (2)
Right arrowRequest Permissions
Google Scholar
Right arrow Articles by Gordon, M. J. C.
Right arrow Search for Related Content
Social Bookmarking
Add to CiteULike   Add to Connotea   Add to Del.icio.us  
What's this?

Relating Event and Trace Semantics of Hardware Description Languages

Michael J. C. Gordon1

1 University of Cambridge Computer Laboratory, William Gates Building, J. J. Thomson Ave, Cambridge CB3 0FD, UK Email: Mike.Gordon@cl.cam.ac.uk

Industry standard hardware description languages like Verilog and VHDL are based on event simulation. Formal verification methods such as theorem proving and model checking are based on the analysis of sets of traces of transition systems or automata. There is a semantic gap between these two interpretations and consequently one cannot be sure that results obtained by simulation and formal verification are consistent. This paper is a step towards bridging this gap. A simple simulation cycle is specified for a Verilog-like language and it is shown how for simple examples of practical interest this can be related to a standard formal-verification-oriented model based on traces.


Add to CiteULike CiteULike   Add to Connotea Connotea   Add to Del.icio.us Del.icio.us    What's this?




Disclaimer:
Please note that abstracts for content published before 1996 were created through digital scanning and may therefore not exactly replicate the text of the original print issues. All efforts have been made to ensure accuracy, but the Publisher will not be held responsible for any remaining inaccuracies. If you require any further clarification, please contact our Customer Services Department.