[clang] [clang][CompundLiteralExpr] Don't defer evaluation for CLEs (PR #137163)

Ilya Biryukov via cfe-commits cfe-commits at lists.llvm.org
Mon Apr 28 02:07:42 PDT 2025


================
@@ -9125,9 +9126,25 @@ bool
 LValueExprEvaluator::VisitCompoundLiteralExpr(const CompoundLiteralExpr *E) {
   assert((!Info.getLangOpts().CPlusPlus || E->isFileScope()) &&
          "lvalue compound literal in c++?");
-  // Defer visiting the literal until the lvalue-to-rvalue conversion. We can
-  // only see this when folding in C, so there's no standard to follow here.
-  return Success(E);
+  APValue *Lit;
+  // If CompountLiteral has static storage, its value can be used outside
+  // this expression. So evaluate it once and store it in ASTContext.
+  if (E->hasStaticStorage()) {
+    Lit = E->getOrCreateStaticValue(Info.Ctx);
+    Result.set(E);
+    // Reset any previously evaluated state, otherwise evaluation below might
+    // fail.
+    // FIXME: Should we just re-use the previously evaluated value instead?
+    *Lit = APValue();
----------------
ilya-biryukov wrote:

I actually think of the opposite. The code here mimics what `MaterializeTemporaryExpr` does and I think it's a good thing because `MaterializeTemporaryExpr` should be the most battle-tested code for similar cases.

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


More information about the cfe-commits mailing list