On Sun, Nov 05, 2023 at 01:39:30PM -0800, Larry Doolittle wrote:
> On Mon, Oct 02, 2023 at 11:04:12PM -0700, Larry Doolittle wrote:
> > [...] working versions are v5.014 and v5.016.
> [and v5.018]
Verilator v5.020 was pushed to upstream git on Jan 1, 2024,
and I can confirm it also does not
On Mon, Oct 02, 2023 at 11:04:12PM -0700, Larry Doolittle wrote:
> [...] working versions are v5.014 and v5.016.
Verilator v5.018 was pushed to upstream git on Oct 31,
and I can confirm it also does not suffer from this bug.
- Larry
Apologies for the possibly confusing typo above.
> I can confirm that the bug shows up in v5.012, but not v5.014 or v6.016.
Of course I mean to say that working versions are v5.014 and v5.016.
Where v5.016 doesn't look properly tagged yet, but is actually commit cef3960a.
- Larry
Package: verilator
Version: 5.012-1+b1
My use case triggers upstream issue 4362
https://github.com/verilator/verilator/issues/4362
Earlier versions of verilator, like 5.006-3 found in bookworm,
do not show the same bug, so it counts as a regression.
I personally built several versions from
4 matches
Mail list logo
