[all-commits] [llvm/llvm-project] c834d1: [clang][bytecode] Fix `evaluateDestruction()` (#20...

[Timm Baeder via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: c834d1acf130b8d98d818b60ab129f780855461f
      https://github.com/llvm/llvm-project/commit/c834d1acf130b8d98d818b60ab129f780855461f
  Author: Timm Baeder <tbaeder at redhat.com>
  Date:   2026-06-25 (Thu, 25 Jun 2026)

  Changed paths:
    M clang/lib/AST/ByteCode/Compiler.cpp
    M clang/lib/AST/ByteCode/Context.cpp
    M clang/lib/AST/ByteCode/EvalEmitter.cpp
    M clang/lib/AST/ByteCode/Interp.cpp
    M clang/lib/AST/ByteCode/InterpFrame.cpp
    M clang/lib/AST/ByteCode/InterpState.h
    M clang/lib/AST/ExprConstant.cpp
    A clang/test/AST/ByteCode/evaluate-dtor.cpp
    M clang/test/CXX/expr/expr.const/p6-2a.cpp
    M clang/test/CodeGenCXX/const-init-cxx2a.cpp
    M clang/test/CodeGenCXX/non-const-init-cxx2a.cpp

  Log Message:
  -----------
  [clang][bytecode] Fix `evaluateDestruction()` (#205778)

Me previous testing regarding this seems to have been insufficient. Or
this regressed some time along the way.

Now that `CLANG_USE_EXPERIMENTAL_CONST_INTERP` is used for testing I
noticed a few regressions.

We need to special-case the evaluating decl in a few places, since it's
a global variable that we're allowed to modify.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications