<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm5719-llvm/lldb/source/API, branch meklort-10.0.1</title>
<subtitle>Project Ortega BCM5719 LLVM</subtitle>
<id>https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1</id>
<link rel='self' href='https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/'/>
<updated>2020-01-10T23:02:21+00:00</updated>
<entry>
<title>[lldb/Reproducer] Add SBReproducer::Replay overload (again)</title>
<updated>2020-01-10T23:02:21+00:00</updated>
<author>
<name>Jonas Devlieghere</name>
<email>jonas@devlieghere.com</email>
</author>
<published>2020-01-10T22:54:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=d3ba1e026dbc44e9097ce6ea1c92d065f1fe33e8'/>
<id>urn:sha1:d3ba1e026dbc44e9097ce6ea1c92d065f1fe33e8</id>
<content type='text'>
I modified the SBAPI under the assumption that nobody was using the old
API yet. However, that turns out to be false. So instead of adding the
deafault argument I've reintroduced the old API and made the new one an
overload.
</content>
</entry>
<entry>
<title>Data formatters: Look through array element typedefs</title>
<updated>2020-01-10T10:45:24+00:00</updated>
<author>
<name>Jaroslav Sevcik</name>
<email>jarin@google.com</email>
</author>
<published>2020-01-10T10:44:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=902974277d507a149e33487d32e4ba58c41451b6'/>
<id>urn:sha1:902974277d507a149e33487d32e4ba58c41451b6</id>
<content type='text'>
Summary:
Motivation: When formatting an array of typedefed chars, we would like to display the array as a string.

The string formatter currently does not trigger because the formatter lookup does not resolve typedefs for array elements (this behavior is inconsistent with pointers, for those we do look through pointee typedefs). This patch tries to make the array formatter lookup somewhat consistent with the pointer formatter lookup.

Reviewers: teemperor, clayborg

Reviewed By: teemperor, clayborg

Subscribers: clayborg, lldb-commits

Tags: #lldb

Differential Revision: https://reviews.llvm.org/D72133
</content>
</entry>
<entry>
<title>[lldb/Bindings] Move bindings into their own subdirectory</title>
<updated>2020-01-09T16:44:34+00:00</updated>
<author>
<name>Jonas Devlieghere</name>
<email>jonas@devlieghere.com</email>
</author>
<published>2020-01-09T15:57:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=6498aff249a1c3c6bad33137df3b90e2973722d6'/>
<id>urn:sha1:6498aff249a1c3c6bad33137df3b90e2973722d6</id>
<content type='text'>
All the code required to generate the language bindings for Python and
Lua lives under scripts, even though the majority of this code aren't
scripts at all, and surrounded by scripts that are totally unrelated.

I've reorganized these files and moved everything related to the
language bindings into a new top-level directory named bindings. This
makes the corresponding files self contained and much more discoverable.

Differential revision: https://reviews.llvm.org/D72437
</content>
</entry>
<entry>
<title>[lldb][NFC] Use static_cast instead of reinterpret_cast where possible</title>
<updated>2020-01-07T12:03:56+00:00</updated>
<author>
<name>Raphael Isemann</name>
<email>teemperor@gmail.com</email>
</author>
<published>2020-01-07T11:13:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=65fdb34219f33b2871a532a38814ac4ebea10abc'/>
<id>urn:sha1:65fdb34219f33b2871a532a38814ac4ebea10abc</id>
<content type='text'>
Summary: There are a few places in LLDB where we do a `reinterpret_cast` for conversions that we could also do with `static_cast`. This patch moves all this code to `static_cast`.

Reviewers: shafik, JDevlieghere, labath

Reviewed By: labath

Subscribers: arphaman, usaxena95, lldb-commits

Tags: #lldb

Differential Revision: https://reviews.llvm.org/D72161
</content>
</entry>
<entry>
<title>[CMake] Add $ORIGIN/../../../../lib to rpath if BUILD_SHARED_LIBS or LLVM_LINK_LLVM_DYLIB on *nix</title>
<updated>2020-01-06T18:01:55+00:00</updated>
<author>
<name>Fangrui Song</name>
<email>maskray@google.com</email>
</author>
<published>2019-12-21T22:59:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=bbfebd7b8a671c9649305b8a5f72e93dd1ef60e1'/>
<id>urn:sha1:bbfebd7b8a671c9649305b8a5f72e93dd1ef60e1</id>
<content type='text'>
Summary:
lib/python2.7/dist-packages/lldb/_lldb.so is a symlink to lib/liblldb.so,
which depends on lib/libLLVM*.so (-DBUILD_SHARED_LIBS=ON) or lib/libLLVM-10git.so
(-DLLVM_LINK_LLVM_DYLIB=ON). Add an additional rpath `$ORIGIN/../../../../lib` so
that _lldb.so can be loaded from Python.

This fixes an import error from lib/python2.7/dist-packages/lldb/__init__.py

  from . import _lldb
  ImportError: libLLVMAArch64CodeGen.so.10git: cannot open shared object file: No such file or directory

 The following configurations will work:

* -DBUILD_SHARED_LIBS=ON
* -DBUILD_SHARED_LIBS=OFF -DLLVM_LINK_LLVM_DYLIB=ON
* -DBUILD_SHARED_LIBS=OFF -DLLVM_LINK_LLVM_DYLIB=ON -DCLANG_LINK_CLANG_DYLIB=ON
  (-DCLANG_LINK_CLANG_DYLIB=ON depends on -DLLVM_LINK_LLVM_DYLIB=ON)

Reviewed By: labath

Differential Revision: https://reviews.llvm.org/D71800
</content>
</entry>
<entry>
<title>[lldb/CMake] Use PYTHON_LIBRARIES instead of PYTHON_LIBRARY</title>
<updated>2020-01-02T21:01:17+00:00</updated>
<author>
<name>Jonas Devlieghere</name>
<email>jonas@devlieghere.com</email>
</author>
<published>2020-01-02T21:00:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=3ddfb04f41ac60529316f64ae5ab1a8ff1cce6e2'/>
<id>urn:sha1:3ddfb04f41ac60529316f64ae5ab1a8ff1cce6e2</id>
<content type='text'>
PYTHON_LIBRARIES is the canonical variable set by FindPythonLibs while
PYTHON_LIBRARY is an implementation detail. This replaces the uses of
the latter with the former.
</content>
</entry>
<entry>
<title>[Lldb/Lua] Generate Lua Bindings</title>
<updated>2019-12-21T19:28:41+00:00</updated>
<author>
<name>Jonas Devlieghere</name>
<email>jonas@devlieghere.com</email>
</author>
<published>2019-12-08T23:32:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=bf03e17c570171c7a52117fe63ace89d58f328d5'/>
<id>urn:sha1:bf03e17c570171c7a52117fe63ace89d58f328d5</id>
<content type='text'>
This patch uses SWIG to generate the Lua bindings for the SB API. It
covers most of the API, but some methods require a type map similar to
Python.

Discussion on the mailing list:
http://lists.llvm.org/pipermail/lldb-dev/2019-December/015812.html

Differential revision: https://reviews.llvm.org/D71235
</content>
</entry>
<entry>
<title>[lldb] Expose more optional dependencies through GetBuildConfiguration()</title>
<updated>2019-12-21T05:01:08+00:00</updated>
<author>
<name>Jonas Devlieghere</name>
<email>jonas@devlieghere.com</email>
</author>
<published>2019-12-21T05:01:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=6cc3ee17a018d916459a4f59a77c75d0b7e191a0'/>
<id>urn:sha1:6cc3ee17a018d916459a4f59a77c75d0b7e191a0</id>
<content type='text'>
Expose all the externally-observable optional dependencies through
SBDebugger::GetBuildConfiguration().
</content>
</entry>
<entry>
<title>[lldb/Lua] Add Boilerplate for a Lua Script Interpreter</title>
<updated>2019-12-19T18:13:51+00:00</updated>
<author>
<name>Jonas Devlieghere</name>
<email>jonas@devlieghere.com</email>
</author>
<published>2019-12-07T23:49:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=67de896229c0f1918f50a48973b7ce0007a181a9'/>
<id>urn:sha1:67de896229c0f1918f50a48973b7ce0007a181a9</id>
<content type='text'>
This adds the boilerplate necessary to support the Lua script
interpreter. The interpreter is not functional yet and just reports that
it's not implemented.

Discussion on the mailing list:
http://lists.llvm.org/pipermail/lldb-dev/2019-December/015812.html

Differential revision: https://reviews.llvm.org/D71232
</content>
</entry>
<entry>
<title>[lldb/CMake] Rename LLDB_DISABLE_PYTHON to LLDB_ENABLE_PYTHON</title>
<updated>2019-12-13T21:41:11+00:00</updated>
<author>
<name>Jonas Devlieghere</name>
<email>jonas@devlieghere.com</email>
</author>
<published>2019-12-13T18:37:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=4e26cf2cfb2b140a33ec236153cb2f23b5c44127'/>
<id>urn:sha1:4e26cf2cfb2b140a33ec236153cb2f23b5c44127</id>
<content type='text'>
This matches the naming scheme used by LLVM and all the other optional
dependencies in LLDB.

Differential revision: https://reviews.llvm.org/D71482
</content>
</entry>
</feed>
