Revision tags: llvmorg-18.1.8, llvmorg-18.1.7, llvmorg-18.1.6, llvmorg-18.1.5, llvmorg-18.1.4, llvmorg-18.1.3 |
|
#
546dc224 |
| 30-Mar-2024 |
Stefan Gränitz <stefan.graenitz@gmail.com> |
[clang-repl] Minor cleanups in Value.cpp (NFC) (#87066)
|
Revision tags: llvmorg-18.1.2, llvmorg-18.1.1, llvmorg-18.1.0, llvmorg-18.1.0-rc4, llvmorg-18.1.0-rc3, llvmorg-18.1.0-rc2, llvmorg-18.1.0-rc1, llvmorg-19-init, llvmorg-17.0.6, llvmorg-17.0.5, llvmorg-17.0.4, llvmorg-17.0.3, llvmorg-17.0.2, llvmorg-17.0.1, llvmorg-17.0.0, llvmorg-17.0.0-rc4, llvmorg-17.0.0-rc3, llvmorg-17.0.0-rc2, llvmorg-17.0.0-rc1, llvmorg-18-init |
|
#
4ad89131 |
| 20-Jul-2023 |
Sindhu Chittireddy <sindhu.chittireddy@intel.com> |
[NFC] Add checks for self-assignment.
Differential Revision: https://reviews.llvm.org/D155776
|
#
fa39c0a5 |
| 24-Jul-2023 |
Michael Platings <michael.platings@arm.com> |
Revert "[NFC] Add checks for self-assignment."
This reverts commit 8ac137acefc01caf636db5f95eb0977c97def1ba.
The code does not compile.
|
#
8ac137ac |
| 20-Jul-2023 |
Sindhu Chittireddy <sindhu.chittireddy@intel.com> |
[NFC] Add checks for self-assignment.
Differential Revision: https://reviews.llvm.org/D155776
|
Revision tags: llvmorg-16.0.6 |
|
#
b0525f66 |
| 04-Jun-2023 |
Manna, Soumi <soumi.manna@intel.com> |
[NFC][CLANG] [NFC][CLANG] Fix nullptr dereference issue in ConvertQualTypeToKind()
This patch uses castAs instead of getAs which will assert if the type doesn't match in ConvertQualTypeToKind(clang:
[NFC][CLANG] [NFC][CLANG] Fix nullptr dereference issue in ConvertQualTypeToKind()
This patch uses castAs instead of getAs which will assert if the type doesn't match in ConvertQualTypeToKind(clang::ASTContext const &, clang::QualType).
Reviewed By: erichkeane
Differential Revision: https://reviews.llvm.org/D151928
show more ...
|
Revision tags: llvmorg-16.0.5 |
|
#
5111286f |
| 23-May-2023 |
Jun Zhang <jun@junz.org> |
Reland "Reland [clang-repl] Introduce Value to capture expression results"
This reverts commit 094ab4781262b6cb49d57b0ecdf84b047c879295.
Reland with changing `ParseAndExecute` to `Parse` in `Interp
Reland "Reland [clang-repl] Introduce Value to capture expression results"
This reverts commit 094ab4781262b6cb49d57b0ecdf84b047c879295.
Reland with changing `ParseAndExecute` to `Parse` in `Interpreter::create`. This avoid creating JIT instance everytime even if we don't really need them.
This should fixes failures like https://lab.llvm.org/buildbot/#/builders/38/builds/11955
The original reverted patch also causes GN bot fails on M1. (https://lab.llvm.org/buildbot/#/builders/38/builds/11955) However, we can't reproduce it so let's reland it and see what happens. See discussions here: https://reviews.llvm.org/rGd71a4e02277a64a9dece591cdf2b34f15c3b19a0
show more ...
|
#
d71a4e02 |
| 18-May-2023 |
Jun Zhang <jun@junz.org> |
Reland [clang-repl] Introduce Value to capture expression results
This reverts commit 7158fd381a0bc0222195d6a07ebb42ea57957bda. * Fixes endianness issue on big endian machines like PowerPC-bl * Disa
Reland [clang-repl] Introduce Value to capture expression results
This reverts commit 7158fd381a0bc0222195d6a07ebb42ea57957bda. * Fixes endianness issue on big endian machines like PowerPC-bl * Disable tests on platforms that having trouble to support JIT
Signed-off-by: Jun Zhang <jun@junz.org>
show more ...
|
Revision tags: llvmorg-16.0.4 |
|
#
a423b7f1 |
| 16-May-2023 |
Jun Zhang <jun@junz.org> |
[clang-repl] Introduce Value to capture expression results
This is the second part of the below RFC: https://discourse.llvm.org/t/rfc-handle-execution-results-in-clang-repl/68493
This patch impleme
[clang-repl] Introduce Value to capture expression results
This is the second part of the below RFC: https://discourse.llvm.org/t/rfc-handle-execution-results-in-clang-repl/68493
This patch implements a Value class that can be used to carry expression results in clang-repl. In other words, when we see a top expression without semi, it will be captured and stored to a Value object. You can explicitly specify where you want to store the object, like:
``` Value V; llvm::cantFail(Interp->ParseAndExecute("int x = 42;")); llvm::cantFail(Interp->ParseAndExecute("x", &V)); ```
`V` now stores some useful infomation about `x`, you can get its real value (42), it's `clang::QualType` or anything interesting.
However, if you don't specify the optional argument, it will be captured to a local variable, and automatically called `Value::dump`, which is not implemented yet in this patch.
Signed-off-by: Jun Zhang <jun@junz.org>
show more ...
|