namhyung wrote:
Also I think it generates variables for destination of pointers, not the
source. For example, if we have `a->b->c`, what we need is variables for `a`
and `b`. Usually it would already have one for `a`, so it can skip generating
it (unless there's a difference like due to type
@@ -5636,6 +5636,31 @@ void
CGDebugInfo::EmitExternalVariable(llvm::GlobalVariable *Var,
Var->addDebugInfo(GVE);
}
+void CGDebugInfo::EmitPseudoVariable(llvm::AllocaInst *Alloca, QualType Ty,
+ SourceLocation Loc) {
+ llvm::DIFile *Unit
https://github.com/huangjd updated
https://github.com/llvm/llvm-project/pull/81545
>From f2c82758e1cba7773e41d941d2812c829c339675 Mon Sep 17 00:00:00 2001
From: William Huang
Date: Mon, 12 Feb 2024 02:27:13 -0500
Subject: [PATCH 1/2] Add option to generate additional info for expression
contai
https://github.com/david-xl commented:
Please add test cases. The clang user manual also needs update.
https://github.com/llvm/llvm-project/pull/81545
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listin
snehasish wrote:
Any measurements of impact to compile time, memory etc on a reasonable size
benchmark (e.g. clang)?
https://github.com/llvm/llvm-project/pull/81545
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin
github-actions[bot] wrote:
:warning: C/C++ code formatter, clang-format found issues in your code.
:warning:
You can test this locally with the following command:
``bash
git-clang-format --diff 9261ab708e37c2d6499ac063045f816d25a5919c
f2c82758e1cba7773e41d941d2812c829c339675 --
https://github.com/huangjd created
https://github.com/llvm/llvm-project/pull/81545
Such expression does not correspond to a variable in the source code thus does
not have a debug location. When the user collects perf data on the program, if
the intermediate memory load instruction is sampled,
