{"id":12743,"date":"2017-02-24T10:15:15","date_gmt":"2017-02-24T17:15:15","guid":{"rendered":"https:\/\/blogs.mentor.com\/verificationhorizons\/?p=12743"},"modified":"2026-03-27T08:38:08","modified_gmt":"2026-03-27T12:38:08","slug":"the-walking-lrm","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/2017\/02\/24\/the-walking-lrm\/","title":{"rendered":"The Walking LRM"},"content":{"rendered":"

My last blog post<\/a> was written a few years ago before attending a conference when I was reminiscing about the 10-year history of SystemVerilog. Now I\u2019m writing about going to another conference, DVCon<\/a>, and being part of a panel<\/a> reminiscing about the 15-year history of SystemVerilog and envisioning its future. My<\/i> history with SystemVerilog goes back much further.<\/p>\n

\"SoulMy first job out of college was working with a group of Data General (DG) engineers made public in the book, Soul of a New Machine<\/i><\/a>, by Tracy Kidder in 1981. Part of my job was writing a program that simulated the microcode of the CPUs we designed. Back then, there were no hardware description languages and you had to hard code everything for each CPU. If you were lucky you could reuse some of the code for the user interface between projects. Later, DG came up with a somewhat more general-purpose simulation language. It was general-purpose in the sense that it could be used for a wider range of projects based on the way DG developed hardware. But getting it to work in another company\u2019s environment would have been a challenge. \u00a0By the way, Badru Agarwala<\/a> was the DG simulation developer I worked with who later founded the Verilog simulation companies Frontline and Axiom. He now manages the Calypto division at Mentor Graphics.<\/p>\n

Many other processor companies like DEC, IBM and Intel had their own in-house simulation languages or were in the process of developing one because no commercially viable technologies existed. Eventually, Phil Moorby at Gateway Design<\/a> began developing the Verilog language and simulator. One of the benefits of having an independent language, although not an official<\/i> standard yet, was you could now share or bring in models from outside your company. This includes being able to hand off a Verilog netlist to another company for manufacturing. Another benefit was that companies could now focus on the design and verification of their products instead of the design and verification of tools that design and verify their products.<\/p>\n

I evaluated Verilog in its first year of release back in 1985\/1986. DG decided not to adopt Verilog at that point, but I liked it so much I left DG and joined Gateway Design as one of its first application engineers. Dropping another name, Karen Bartleson was one of my\u00a0first customers as a CAD manager working at UTMC<\/a>. She recently took the office of President and CEO of the IEEE<\/a>.<\/p>\n

\"IEEE\"Fast forward to the next decade, when Verilog became standardized as IEEE 1364-1995. But by then it had already lost ground in the verification space. Companies went back to developing their own in-house verification solutions. Sun Microsystems developed Vera<\/a> and later released it as a commercial product marketed by Systems Science. Arturo Salz<\/a> was one of its developers and will be on the DVCon panel<\/a> with me as well. Specman<\/a> was developed for National Semiconductor and a few other clients and later marketed by Verisity<\/a>. Once again, we had the problem of competing independent languages and therefore limiting the ability to share or acquire verification models. So, in 1999, a few Gateway alums and others formed a startup<\/a> which I joined a year later hoping to consolidate design and verification back into one standard language. That language was SUPERLOG and became the starting point for the Accellera SystemVerilog 3.0<\/a> standard in 2002, fifteen years ago.<\/p>\n

\"IEEEThere are many dates you could pick for the start of SystemVerilog. You could claim it couldn\u2019t exist until there was a simulator supporting some of the features in the standard. For me, it started when I first read an early Verilog Language Reference Manual and executed my first initial<\/strong> block 31 years ago. I\u2019ve been using Verilog almost every day since. And now all of Verilog is part of SystemVerilog. I\u2019ve been so much a part of the development of the language from its early beginnings; that\u2019s why some of my colleagues call me \u201cThe Walking LRM\u201d. Luckily, I don\u2019t dream about it. I hope I never get called \u201cThe Sleeping LRM\u201d.<\/p>\n

So, what\u2019s next for SystemVerilog? Are we going to repeat the cycle of fragmentation and re-consolidation? Various extensions have already begun showing up in different implementations. SystemVerilog has become so complex that no one can keep a good portion of it in their head anymore. It is very difficult to remove anything once it is in the LRM. Should we start over? We tried to do that with SUPERLOG, but no one adopted it until it was made fully backward compatible with Verilog.<\/p>\n

The Universal Verification Methodology<\/a> (UVM) was designed to cut down the complexity of learning and using SystemVerilog. There are now a growing number of sub-methodologies for using the UVM because the UVM itself has exploded in complexity \u00a0(UVM Framework<\/a> and Easier UVM<\/a> to name a couple). I have also taken my own approach when teaching people SystemVerilog by showing a minimal subset (See my SystemVerilog OOP for UVM Verification<\/a> course).<\/p>\n

\"DVCon\"<\/a>I do believe in the KISS principle<\/a> of Engineering and I hope that is what prevails in the next version of SystemVerilog, whether we start over or just make refinements. I hope you will be able to join the discussion with others and me at the DVCon panel<\/a> next week, or in the forums in the Verification Academy<\/a>, or on Twitter<\/a>.<\/p>\n

-Dave<\/em><\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

My last blog post was written a few years ago before attending a conference when I was reminiscing about the…<\/p>\n","protected":false},"author":71589,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spanish_translation":"","french_translation":"","german_translation":"","italian_translation":"","polish_translation":"","japanese_translation":"","chinese_translation":"","footnotes":""},"categories":[1],"tags":[307,313,326,442,506,528,533,540,718,732,751,787,831],"industry":[],"product":[],"coauthors":[],"class_list":["post-12743","post","type-post","status-publish","format-standard","hentry","category-news","tag-307","tag-313","tag-accellera","tag-dvcon","tag-functional-verification","tag-ieee","tag-ieee-1800","tag-ieee-sa","tag-simulation","tag-standards","tag-systemverilog","tag-uvm","tag-verilog"],"_links":{"self":[{"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/posts\/12743","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/users\/71589"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/comments?post=12743"}],"version-history":[{"count":1,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/posts\/12743\/revisions"}],"predecessor-version":[{"id":19841,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/posts\/12743\/revisions\/19841"}],"wp:attachment":[{"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/media?parent=12743"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/categories?post=12743"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/tags?post=12743"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/industry?post=12743"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/product?post=12743"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/coauthors?post=12743"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}