Catherine
Catherine
Something that I realized is that this class would also be really convenient for specifying frequencies of clocks. `amaranth.time`?
Oh, if I knew this was planned, I would not have [added this workaround to boost::filesystem](https://github.com/boostorg/filesystem/pull/144/files#diff-ef3cb21bb79a3b4f51c5ee8e8a28ee106a1c6ef1d441866d2d4c27adce982eafR1567). (Mainly commenting for the benefit of people who look at both of these issues...
> Figure how to feed debug info into the tool to get flame graphs with > proper line information (instead of just PC addresses). This sounds tricky to > me...
@japaric I think you need to call `LLVMContextSetDiagnosticHandler`. But probably a better idea is an LLVM patch that exposes this data directly in a proper format.
Denominating from 0.3 because this issue requires #228.
This is indeed a serious issue that I was considering as a part of #228, but it's important enough to have its own bug too. What you suggest would work,...
It was the intended behavior originally. However, I have some plans for a new Verilog/RTLIL backend, which would reuse identical subexpressions. There is no ETA on that.
Duplicate of #28.
Thank you!
CI is fixed now. There's a workaround for downgrading MarkupSafe with Amaranth 0.3.