Revision tags: llvmorg-21-init, llvmorg-19.1.7, llvmorg-19.1.6, llvmorg-19.1.5 |
|
#
ceaf6e91 |
| 25-Nov-2024 |
Timm Baeder <tbaeder@redhat.com> |
[clang][bytecode] Support ImplicitValueInitExpr for multi-dim arrays (#117312)
The attached test case from https://github.com/llvm/llvm-project/issues/117294 used to cause an assertion because we ca
[clang][bytecode] Support ImplicitValueInitExpr for multi-dim arrays (#117312)
The attached test case from https://github.com/llvm/llvm-project/issues/117294 used to cause an assertion because we called classifPrim() on an array type.
The new result doesn't crash but isn't exactly perfect either. Since the problem arises when evaluating an ImplicitValueInitExpr, we have no proper source location to point to. Point to the caller instead.
show more ...
|
Revision tags: llvmorg-19.1.4, llvmorg-19.1.3, llvmorg-19.1.2, llvmorg-19.1.1 |
|
#
4b964002 |
| 24-Sep-2024 |
Timm Baeder <tbaeder@redhat.com> |
[clang][bytecode] Allow placement-new in std functions pre-C++26 (#109753)
|
#
898fd396 |
| 23-Sep-2024 |
Timm Baeder <tbaeder@redhat.com> |
[clang][bytecode] Check allocation size limit for operator new (#109590)
|
Revision tags: llvmorg-19.1.0 |
|
#
d03822d8 |
| 11-Sep-2024 |
Timm Baeder <tbaeder@redhat.com> |
[clang][bytecode] Fix lookup of source locations in implicit ctors (#107992)
Implicit functions may still have a body. The !hasBody() check is
enough.
|
#
83fea8b8 |
| 07-Sep-2024 |
Timm Baeder <tbaeder@redhat.com> |
[clang][bytecode] Allow continuing when discarded MemberExpr Base fails (#107231)
We don't need the value in this case, since we're discarding it anyway.
Allow continuing the interpretation but not
[clang][bytecode] Allow continuing when discarded MemberExpr Base fails (#107231)
We don't need the value in this case, since we're discarding it anyway.
Allow continuing the interpretation but note the side effect.
show more ...
|
Revision tags: llvmorg-19.1.0-rc4 |
|
#
733a92d7 |
| 03-Sep-2024 |
Timm Baeder <tbaeder@redhat.com> |
[clang][bytecode] Print Pointers via APValue (#107056)
Instead of doing this ourselves, just rely on printing the APValue.
|
#
d9e72860 |
| 26-Aug-2024 |
yronglin <yronglin777@gmail.com> |
[NFC][clang][bytecode] Rename `clang::interp::State::getCtx` to `clang::interp::State::getASTContext` (#106071)
The new constant interpreter's `clang::interp::InterpState` contains
both `clang::int
[NFC][clang][bytecode] Rename `clang::interp::State::getCtx` to `clang::interp::State::getASTContext` (#106071)
The new constant interpreter's `clang::interp::InterpState` contains
both `clang::interp::Context` and `clang::ASTContext`. So using `S.Ctx`
and `S.getCtx()` was a bit confusing. This PR rename `getCtx()` to
`getASTContext` to make things more clearer.
Signed-off-by: yronglin <yronglin777@gmail.com>
show more ...
|
Revision tags: llvmorg-19.1.0-rc3 |
|
#
a07aba5d |
| 16-Aug-2024 |
Timm Baeder <tbaeder@redhat.com> |
[clang] Rename all AST/Interp stuff to AST/ByteCode (#104552)
"Interp" clashes with the clang interpreter and people often confuse
this.
|