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

[J. Ryan Stinnett via llvm-commits]

jryans wrote:

> @jryans See the ocaml binding in tree for instance. Typically, no tool is run at all. Header (or any equivalent, that would be module interface in OCaml) are simply being translated, manually or assisted by tools.

Hmm, I guess I am still not quite understanding the problem, apologies... If the translation is manual, then a human could presumably "mentally" expand the macro and / or manually run the C preprocessor as part of their manual translation. If the translation is automated, feed it the output of the C preprocessor.

I am not really understanding how the use of macros / the `.def` file creates an obstacle, since both manual and automated translation would appear to have a path forward. It's clear that you believe it **does** create an obstacle though, so I feel like I am missing part of the story...

>From the LLVM side, I agree with @dwblaikie that we'd like to avoid having multiple copies of these DWARF codes lying around if possible. Beyond just the standardised codes, there are also various extensions as well that come from different sources, so it's much easier to manage that complexity (within LLVM at least) in a single place.

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