
2025-07-28 05:52:50
It's always a good day when you have "always comb foo = bar" and using foo instead of bar changes the run time of your simulation by almost 100K clock cycles.
I have to assume this is a Vivado simulator bug present in both 2024.1 and 2025.1, but don't yet have a fully reduced test case other than an always_ff block somehow having input and output changing on the same clock edge.