Keep unmangled fully qualified function name in cir.func

[keryell]

CIR code with a lot of functions is difficult to read & debug because of the mangling names.
If the unmangled fully qualified function name is an attribute of cir.func, it can be displayed in IDE/editors for example by a hoover with usual LSP tooling.

[bcardosolopes]

I usually pipe the output into c++-filt but I can also see that being handy. Perhaps we could implement that by using an optional attribute and linking that to the presence of some new cc1 compiler flag (or perhaps when -g is present, or something like that).

[keryell]

Ouch, actually C++filt is liberal enough to process an MLIR file reasonably well. 🤯.
We need an MLIR version adding "" around symbols because my LSP server chokes on @aie::tile<1, 4> aie::device<(aie::$_0)42>::tile<1, 4>() but seems ok with @"aie::tile<1, 4> aie::device<(aie::$_0)42>::tile<1, 4>()". 😄

[bcardosolopes]

LLVM has llvm-cxxfilt which seems to be almost identical cmdline interface, perhaps that would be an extension LLVM project would be willing to accept? (Like an extra knob to quote the symbols)

[keryell]

LLVM has llvm-cxxfilt which seems to be almost identical cmdline interface, perhaps that would be an extension LLVM project would be willing to accept? (Like an extra knob to quote the symbols)

This looks like a great idea and it looks like it even works 😄 llvm/llvm-project#111871
The main issue I hit was the case with module-level allocation where some symbols are already quoted between "" I had to handle to avoid double-quoting.