[llvm] [C API] Add bindings for DWARF type encoding. (PR #102171)

[David Blaikie via llvm-commits]

dwblaikie wrote:

> Yes, but this isn't really the reason why people want a C API, and this isn't how the vast majority of the C API users use it. The `.def` solution here is (or any technique that rely on the preprocessor in general) is a net negative.

Do you have references to the tooling you've referred to that needs to read C headers, but can't handle preprocessing them first?

> I'm not sure I understand the concern with maintenance here. The value come from the DWARF spec. If these value change, everything is broken and a couple of entry in an enum in a C API will be the least of our concerns.

Not so much concerned about the current values changing, but maintaining the list going forward when new entries are needed - we have one place in LLVM to update at the moment. I don't think we should add a second.

https://github.com/llvm/llvm-project/pull/102171