Project Ortega BCM5719 LLVM https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1 2019-12-18T20:54:04+00:00 2019-12-18T20:54:04+00:00 Jonas Devlieghere jonas@devlieghere.com 2019-12-18T20:49:46+00:00 urn:sha1:e194d890126007bc8e5acb655f007ef76002edb7 Remove the hack that populates the cpsr register in the gpr struct by writing past the end of the array. This was tripping up ASan. Patch by: Reva Cuthbertson 2019-12-13T18:00:59+00:00 Jonas Devlieghere jonas@devlieghere.com 2019-12-12T18:00:45+00:00 urn:sha1:3011d55f725e280fe29a49bd70a2e0157587b17a Rename LLDB_DISABLE_POSIX to LLDB_ENABLE_POSIX and use cmakedefine01 for consistency. 2019-11-13T22:53:13+00:00 Davide Italiano ditaliano@apple.com 2019-11-13T22:52:52+00:00 urn:sha1:294ef766e8f13818369c22fbad47283c84d87c2f 2019-11-04T18:36:58+00:00 Michał Górny mgorny@gentoo.org 2019-10-31T16:04:35+00:00 urn:sha1:6eca4f46912a8318d7a5888506c3f26c20bdc012 Add info for all register sets supported in NetBSD, particularly for all registers 'expected' by LLDB. This is necessary in order to fix python_api/lldbutil/iter/TestRegistersIterator.py test that currently fails due to missing names of register sets (None). This copies fpreg descriptions from Linux, and combines Linux' AVX and MPX registers into a single XState group, to fit NetBSD register group design. Technically, we do not support MPX registers at the moment but gdb-remote insists on passing their errors anyway, and if we do not include it in any group, they end up in a separate anonymous group that breaks the test. While at it, swap the enums for XState and DBRegs to match register set ordering. This also adds a few consts to the lldb-x86-register-enums.h to provide more consistency between user registers and debug registers. Differential Revision: https://reviews.llvm.org/D69667 2019-10-31T09:58:17+00:00 Guilherme Andrade guiandrade@google.com 2019-10-31T09:46:58+00:00 urn:sha1:e46c6644db8432584e82ef7ddfc9d0f36543f205 Summary: This change increases the offset of MPX registers (by 128) so they do not overlap with the offset associated with AVX registers. That was causing MPX data in GDBRemoteRegisterContext::m_reg_data to get overwritten. Reviewers: labath Reviewed By: labath Subscribers: JDevlieghere, lldb-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D68874 2019-10-17T19:56:40+00:00 Adrian Prantl aprantl@apple.com 2019-10-17T19:56:40+00:00 urn:sha1:1ad655e255090620705eb4ce85d869a54d971912 This patch removes the size_t return value and the append parameter from the remainder of the Find.* functions in LLDB's internal API. As in the previous patches, this is motivated by the fact that these parameters aren't really used, and in the case of the append parameter were frequently implemented incorrectly. Differential Revision: https://reviews.llvm.org/D69119 llvm-svn: 375160 2019-10-16T19:14:49+00:00 Jason Molenda jmolenda@apple.com 2019-10-16T19:14:49+00:00 urn:sha1:7dd7a3607596a51044b8706ebf6df2e613ce1e9b that runs on arm64 ISA targets, specifically Apple watches. Differential Revision: https://reviews.llvm.org/D68858 llvm-svn: 375032 2019-10-11T09:03:29+00:00 Aleksandr Urakov aleksandr.urakov@jetbrains.com 2019-10-11T09:03:29+00:00 urn:sha1:30c2441a3262228990b5317eb3bc2b24ff06d316 This patch adds an implementation of unwinding using PE EH info. It allows to get almost ideal call stacks on 64-bit Windows systems (except some epilogue cases, but I believe that they can be fixed with unwind plan disassembly augmentation in the future). To achieve the goal the CallFrameInfo abstraction was made. It is based on the DWARFCallFrameInfo class interface with a few changes to make it less DWARF-specific. To implement the new interface for PECOFF object files the class PECallFrameInfo was written. It uses the next helper classes: - UnwindCodesIterator helps to iterate through UnwindCode structures (and processes chained infos transparently); - EHProgramBuilder with the use of UnwindCodesIterator constructs EHProgram; - EHProgram is, by fact, a vector of EHInstructions. It creates an abstraction over the low-level unwind codes and simplifies work with them. It contains only the information that is relevant to unwinding in the unified form. Also the required unwind codes are read from the object file only once with it; - EHProgramRange allows to take a range of EHProgram and to build an unwind row for it. So, PECallFrameInfo builds the EHProgram with EHProgramBuilder, takes the ranges corresponding to every offset in prologue and builds the rows of the resulted unwind plan. The resulted plan covers the whole range of the function except the epilogue. Reviewers: jasonmolenda, asmith, amccarth, clayborg, JDevlieghere, stella.stamenova, labath, espindola Reviewed By: jasonmolenda Subscribers: leonid.mashinskiy, emaste, mgorny, aprantl, arichardson, MaskRay, lldb-commits, llvm-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D67347 llvm-svn: 374528 2019-10-08T20:47:44+00:00 Vedant Kumar vsk@apple.com 2019-10-08T20:47:44+00:00 urn:sha1:4805c817c3fa506cf0d17af1960de57bc1538afb LLDB appears to have at least partial support for PPC, but PPC on Mach isn't a thing AFAIK. Differential Revision: https://reviews.llvm.org/D68661 llvm-svn: 374114 2019-10-08T19:40:13+00:00 Vedant Kumar vsk@apple.com 2019-10-08T19:40:13+00:00 urn:sha1:07c5f2a9b0add36974250cd9ab9152458e8b3361 llvm-svn: 374106