[clang] [clang][bytecode] Don't add an LValuePath to APValues with invalid bases (PR #226096)

[via cfe-commits]

llvmorg-github-actions[bot] wrote:


<!--LLVM PR SUMMARY COMMENT-->

@llvm/pr-subscribers-clang

Author: Timm Baeder (tbaederr)

<details>
<summary>Changes</summary>

If the APValue is created for an opaque pointer, check first if the base is valid. If not, we're not supposed to provide an LValuePath at all.

---
Full diff: https://github.com/llvm/llvm-project/pull/226096.diff


4 Files Affected:

- (modified) clang/lib/AST/ByteCode/Compiler.cpp (+32-30) 
- (modified) clang/lib/AST/ByteCode/Pointer.cpp (+31-15) 
- (modified) clang/lib/AST/ByteCode/Pointer.h (+1) 
- (modified) clang/test/CodeGenCXX/mangle-class-nttp.cpp (+3) 


``````````diff
The server is unavailable at this time. Please wait a few minutes before you try again.
``````````

</details>


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