| commit | 2759e47067ea286f6302adcfe93b653cfaf6f2eb | |
| author | Vassil Vassilev <v.g.vassilev@gmail.com> | |
| Sun, 21 Jan 2024 01:00:38 +0000 (21 03:00 +0200) | ||
| committer | GitHub <noreply@github.com> | |
| Sun, 21 Jan 2024 01:00:38 +0000 (20 17:00 -0800) | ||
| tree | 47c3b71d578e0299bd09aee75397a1b550480f62 | treesnapshot (tar.gz zip) |
| parent | dedc7d4d362b8045c6810f8ca7f947bbdb63b7ec | commitdiff |
[clang-repl] We do not need to call new in the object allocation. (#78843)
This test demonstrates template instantiation via the interpreter code.
In order to do that we can allocate the object on the stack and extend
its lifetime by boxing it into a clang::Value.
That avoids the subtle problem where we call the new operator on an
object only known to the interpreter and we cannot destroy it from
compiled code since there is not suitable facility in clang::Value yet.
That should resolve the asan issues that was reported in
llvm/llvm-project#76218.
This test demonstrates template instantiation via the interpreter code.
In order to do that we can allocate the object on the stack and extend
its lifetime by boxing it into a clang::Value.
That avoids the subtle problem where we call the new operator on an
object only known to the interpreter and we cannot destroy it from
compiled code since there is not suitable facility in clang::Value yet.
That should resolve the asan issues that was reported in
llvm/llvm-project#76218.
| clang/unittests/Interpreter/InterpreterTest.cpp | diffblobblamehistory |