[clang] [DebugInfo] Init DwarfVersion of MCOptions like the other. (PR #146666)

https://github.com/Sockke updated https://github.com/llvm/llvm-project/pull/14 >From 1a402b04e60ef3c74c8a3a7ecb3ef0439415d6ec Mon Sep 17 00:00:00 2001 From: Sockke Date: Wed, 2 Jul 2025 16:54:29 +0800 Subject: [PATCH 1/3] Init DwarfVersion of MCOptions like the other. --- clang/lib/CodeGe

[clang] [DebugInfo] Init DwarfVersion of MCOptions like the other. (PR #146666)

Sockke wrote: > I guess this would be visible when using clang to compile some assembly code > and requesting debug info of a specific version We have pre-built bitcode. When compiling bitcode, we need to request specific debug info version - like Distributed ThinLTO's backend process - to kee

[clang] [DebugInfo] Init DwarfVersion of MCOptions like the other. (PR #146666)

Sockke wrote: Sorry for the noise - wrong reviewers were tagged by mistake. https://github.com/llvm/llvm-project/pull/14 ___ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

[clang] [DebugInfo] Init DwarfVersion of MCOptions like the other. (PR #146666)

@@ -51,6 +51,16 @@ // RUN: not %clang -target powerpc64-ibm-aix-xcoff -gdwarf-5 -S -emit-llvm -o - %s 2>&1| \ // RUN: FileCheck %s --check-prefix=UNSUPPORTED-VER5 +// Check what version of dwarf is used to emit debug info when compiling ir with clang. +// RUN: %clang -targ

[clang] [DebugInfo] Init DwarfVersion of MCOptions like the other. (PR #146666)

https://github.com/Sockke created https://github.com/llvm/llvm-project/pull/14 Should the backend's DwarfVersion be initialized like other options? Previously, -gdwarf-xxx did not take effect in the backend—was there a specific reason for this? >From 1a402b04e60ef3c74c8a3a7ecb3ef0439415d6