After a long hiatus, I finally wrote a new blog post: blog.verificationgentleman.com/2026/03/01/c... . 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
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 few iterations of trying to edit the wrong file, removing <' markers from working code and using HTML brackets before succeeding.
@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". π
If anyone one uses #DSim, I'd appreciate some help on this: community.altair.com/discussion/6...
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.
Funnily enough, the quote comes from the Perforce website: www.perforce.com/blog/vcs/git...
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. ".
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. π
E.g. VS Code has doesn't like symlinks for indexing or refreshing Git status.
Absolutely necessary for IT to change $HOME from `/home/<user>` to `/<company-ticker>home/<user>` (where `/<company-ticker>home` is a symlink to `/home`). Absolutely necessary for all the little issues it causes with various programs (like VS Code) that don't like to traverse symlinks
Thanks, I think the same as you. What was confusing in the initial post was that all the other elements in the list are positive and that you also used ">shared ownership". It made it sound like code ownership is better.
Could you elaborate a bit on "code ownership" vs. "shared ownership"?
Also stealing "edit, pray, debug", fits so well with my industry.
Just finished learning how to build my first Astro blog! Check it out at docs.astro.build
via @astro.build
I was doing some productive procrastination by going through the tutorial for @astro.build and I have to say that it's absolutely fantastic. It introduces concepts progressively, let's the user make mistakes and then shows how to fix them, and is just all around easy to follow.
Yet again, I run into the problem that a crappy #semiEDA tool wrapper can't properly handle multi-token arguments (i.e. `wrapper --tool-arg 'some value'` leads to something like `tool --arg some value`). I'm getting pretty sick and tired of running into this again and again and again.
Why is careful commit naming useless on some teams? (I'm guessing this doesn't mean just using "upd" or "change" as a commit message.)
Using @gitlab.com and think it would be better if you wouldn't get horizontal scroll bars for long commit message lines? Leave a thumbs up here:
True dat! Same also applies to test benches. Still, somehow the industry has too much of a fondness for code generation, usually as a first resort.
Sometimes while having to work on projects developed by various "experts", I look at the screen and think "with code like this, who needs enemies?".
I just used `git bisect` for the first time to find a broken commit. I feel like a wizard!
Makes me wonder why there isn't a "SystemVerilog" group, like there is for SystemC.
Where does one normally ask questions to clarify contents of the SystemVerilog standard? StackOverflow doesn't feel like the best place for this somehow. On the Accellera forums there's the "UVM SystemVerilog Discussions" section, but that should be for UVM related stuff.
It's time for me to also jump on the Bluesky bandwagon.
