dblaikie added a comment. Don't know that I've got it in me right now to do the more invasive change of updating the LLVM DebugInfo IR metadata to carry the DWARFv6 style language+version stuff (perhaps especially if that's going to go alongside the DWARFv5 and earlier pure language encoding)
I could do the minimum and fix the C version case to use the DWARFv5-shipped C11 encoding. And perhaps add the post-v5 backported language encodings to LLVM so at least llvm-dwarfdump can detect/render/handle them correctly for name printing, etc. Or I could maybe do something in between - where the post-v5 backported language codes could be used in the IR and then LLVM could detect those and remap them to v5-shipped DW_AT_language + v6-not-ready-yet (using an extension form? Using the form that's not shipped in v6 yet?) attributes? Seems like it's probably not worth emitting the v6 stuff until it's baked. And not worth emitting the post-v5 backported attributes due to risk of breakage? So maybe just do the minimum? Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D138597/new/ https://reviews.llvm.org/D138597 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
