Tootfinder

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.

Suppose I have a staging directory with files to install. For example:
/tmp/foo/usr/local/bin/bar
/tmp/foo/usr/local/lib/libbar.a
I want a tool where I can say 'some-tool install /tmp/foo' and it will copy those files to the real /usr/local/bin and /usr/local/lib.
But it will also back up the old contents of those paths (if any).
Then I can run 'some-tool uninstall /tmp/foo’, and it will delete all the installed files and restore the backed-up files.…

I'm reading papers about recursion and paper A is like "paper B did foo" so I go to check paper B and it's like "paper A did bar"... does this have a fixed point