You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which I build with the command: dfg-opt main.mlir --convert-std-to-circt --convert-dfg-to-circt --convert-fsm-to-sv --lower-seq-to-sv --export-split-verilog
and then throws an error: dfg-opt: /home/gareth/software-repos/mlir_related/dfg-mlir-240522/circt/llvm/llvm/include/llvm/ADT/ArrayRef.h:443: T &llvm::MutableArrayRef<mlir::BlockArgument>::operator[](size_t) const [T = mlir::BlockArgument]: Assertion Index < this->size() && "Invalid index!"' failed..
If I comment out the line: %l_a__3_d0_0 = arith.constant 0 : i32 then things seem to work. For context, I am default initializing a variable to 0 and then assigning a token from dfg.pull from that node, so the l_a__3_d0_0 operand ends up never getting used. Its not common but can happen depending on the code compiled. It seems strange that an unused operation would cause such a crash.
The text was updated successfully, but these errors were encountered:
I have a bug where the hls mlir file is not generating correctly under some conditions:
I have the following main.mlir file
Which I build with the command:
dfg-opt main.mlir --convert-std-to-circt --convert-dfg-to-circt --convert-fsm-to-sv --lower-seq-to-sv --export-split-verilog
This generates the following hls_Temp_calc.mlir:
and then throws an error:
dfg-opt: /home/gareth/software-repos/mlir_related/dfg-mlir-240522/circt/llvm/llvm/include/llvm/ADT/ArrayRef.h:443: T &llvm::MutableArrayRef<mlir::BlockArgument>::operator[](size_t) const [T = mlir::BlockArgument]: Assertion Index < this->size() && "Invalid index!"' failed.
.If I comment out the line:
%l_a__3_d0_0 = arith.constant 0 : i32
then things seem to work. For context, I am default initializing a variable to 0 and then assigning a token from dfg.pull from that node, so the l_a__3_d0_0 operand ends up never getting used. Its not common but can happen depending on the code compiled. It seems strange that an unused operation would cause such a crash.The text was updated successfully, but these errors were encountered: