Open axeabc opened 1 week ago
Adding the --convert-func-to-llvm
flag before using --ensure-debug-info-scope-on-llvm-func
seems to solve the problem. This ensures that function operations are first lowered to LLVM, which then allows the debug info subprogram attributes to be correctly materialized.
Adding the
--convert-func-to-llvm
flag before using--ensure-debug-info-scope-on-llvm-func
seems to solve the problem. This ensures that function operations are first lowered to LLVM, which then allows the debug info subprogram attributes to be correctly materialized.
So, --ensure-debug-info-scope-on-llvm-func
option can't be used alone? Should it be accompanied by some error handling instead of just throwing crash?
git version: 8168088f0a9015b
system:
Ubuntu 18.04.6 LTS
reproduce with:
mlir-opt -ensure-debug-info-scope-on-llvm-func a.mlir
a.mlir:
stack trace: