[all-commits] [llvm/llvm-project] a52054: [lldb] Move ObjectFileJIT to lldbExpression

[Alex via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: a52054cfa29d665c43141c66c20a7b8f7a96b546
      https://github.com/llvm/llvm-project/commit/a52054cfa29d665c43141c66c20a7b8f7a96b546
  Author: Alex Langford <alangford at apple.com>
  Date:   2023-03-31 (Fri, 31 Mar 2023)

  Changed paths:
    M lldb/include/lldb/Expression/IRExecutionUnit.h
    A lldb/include/lldb/Expression/ObjectFileJIT.h
    M lldb/include/lldb/Symbol/ObjectFile.h
    M lldb/source/Expression/CMakeLists.txt
    M lldb/source/Expression/IRExecutionUnit.cpp
    A lldb/source/Expression/ObjectFileJIT.cpp
    M lldb/source/Plugins/ObjectFile/CMakeLists.txt
    R lldb/source/Plugins/ObjectFile/JIT/CMakeLists.txt
    R lldb/source/Plugins/ObjectFile/JIT/ObjectFileJIT.cpp
    R lldb/source/Plugins/ObjectFile/JIT/ObjectFileJIT.h

  Log Message:
  -----------
  [lldb] Move ObjectFileJIT to lldbExpression

In the spirit of not having lldbExpression rely on plugins, this move
makes the most sense. ObjectFileJIT is not really a "plugin" in the
sense that without it, expression evaluation doesn't work at all. This
is different than something like ObjectFileELF where lldb can still
technically debug non-ELF targets without it. For that reason, moving
ObjectFileJIT into Expression where it will be used in conjunction with
IRExecutionUnit makes the most sense.

Differential Revision: https://reviews.llvm.org/D147084