Tudor Timi

@tudortimi
4 Followers
1 Following
19 Posts
Verification Engineer by day, Verification Gentleman by night. Posts may contain traces of snark and/or sarcasm.
Websitehttps://blog.verificationgentleman.com/
GitHubhttps://github.com/tudortimi/
After a long hiatus, I finally wrote a new blog post: https://blog.verificationgentleman.com/2026/03/01/coverage-extensibility-in-systemverilog-2023 . This one's about the "embedded covergroup inheritance" feature added to SystemVerilog by IEEE 1800-2023. Is what I wrote in 2015 about coverage extensibility now obsolete? Read the post to find out!
Coverage Extensibility in SystemVerilog-2023

Quite a while back I wrote a series of posts about coverage extensibility in SystemVerilog. In the first post we looked at how to use policy classes to implement extensible coverage collectors, where ignore bins can be tweaked via class parameters. The second post explored a dynamic flavor of this approach, using constructor arguments instead. Finally, the third post tied everything together by looking at how these approaches interact with UVM and the factory.

Verification Gentleman Blog
I joke, but in all seriousness, I am an AI optimist. It's just going to take a bit more effort from us digital verification folks.

Who says @GitHubCopilot can't be used for underrepresented languages like e (IEEE 1647)?

I asked it to fix this error in #Specman and it managed to do it! It only took a couple of iterations of trying to edit the wrong file, to remove <' and '> markers from working code, to use HTML opening and closing brackets and finally to add the lines mentioned in the error output to the file mentioned in the error output.

@GitHubCopilot made my day again by flagging some code as matching similar code, which actually turned out to be from one of my repos. Well, one of my repos and that of someone who copied it.

Had a look at the link. Seems like the author is 神秘人, which Google translates as "mysterious man". 😂

Print functional coverage bins in report - Altair Community

I recently learned how to generate a metrics report out of simulation, using dcreport. I'm collecting some functional coverage, with some covergroups with coverpoints and crosses. I opened the generated XML and clicked on one of the covergroups: The report only shows the percentage of hits, but not details about what is…

Altair Community
For all the talk about covergroup inheritance in #systemverilog that one can find online since 2023, it seems that EDA vendors couldn't really be bothered to implement it.

I found a quote that very summarizes one of my main reasons for preferring Git over other version control systems:

"Git isn't just a version control system, but part of a broader, highly integrated toolset that many teams rely on daily. ".

Funnily enough, the quote comes from the Perforce website: https://www.perforce.com/blog/vcs/git-vs-perforce-how-choose-and-when-use-both

Git vs. Perforce P4: How to Choose (and When to Use Both) | Perforce Software

Git and Perforce P4 both provide version control solutions. Git has been widely adopted for smaller code-only projects. And Perforce version control software (Helix Core) is known for enterprise-grade performance. Compare Git vs. Perforce P4.

Perforce Software
That feeling when GitHub Copilot warns you that it found similar code to what it generated and then it points you to your own repo. 😎
@mb I think I get what you mean with the wrapper task. My experience has been to use options for testing related tasks, where it actually does need to run most of the build to be able to run tests.
@mb Could you expand on the point about task options being an anti-pattern and there being better options for CLIs?