Project Ortega BCM5719 LLVM https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1 2020-06-23T21:35:35+00:00 2020-06-23T21:35:35+00:00 Nico Weber thakis@chromium.org 2020-01-17T00:04:08+00:00 urn:sha1:0777c907268a8197de102f3770432b0f185de30a When LLVM_APPEND_VC_REV=OFF is set, the current git hash is no longer embedded into binaries (mostly for --version output). Without it, most binaries need to relink after every single commit, even if they didn't change otherwise (due to, say, a documentation-only commit). LLVM_APPEND_VC_REV is ON by default, so this doesn't change the default behavior of anything. With this, all clients of GenerateVersionFromVCS.cmake honor LLVM_APPEND_VC_REV. Differential Revision: https://reviews.llvm.org/D72855 (cherry picked from commit fb5fafb23cc2d8613f8be2487afe94d8594a88ce) 2020-05-19T01:24:44+00:00 Martin Storsjö martin@martin.st 2020-03-28T23:33:55+00:00 urn:sha1:aba4e3fa3bd0aad13168f2f6e8f1874f9a0fdb57 The RuntimeFunction struct, which PECallFrameInfo interprets, has a different layout and differnet semantics on all architectures. Differential Revision: https://reviews.llvm.org/D77000 (cherry picked from commit aa786b881fc89a2a9883bff77912f2053126f95b) 2020-03-03T13:31:05+00:00 Hans Wennborg hans@chromium.org 2020-03-03T08:45:14+00:00 urn:sha1:5f9211bc46fa1a8d1db3a2bc27c2b115cd617795 and follow-ups: a2ca1c2d "build: disable zlib by default on Windows" 2181bf40 "[CMake] Link against ZLIB::ZLIB" 1079c68a "Attempt to fix ZLIB CMake logic on Windows" This changed the output of llvm-config --system-libs, and more importantly it broke stand-alone builds. Instead of piling on more fix attempts, let's revert this to reduce the risk of more breakages. (cherry picked from commit 916be8fd6a0a0feea4cefcbeb0c22c65848d7a2e) 2020-02-19T13:20:34+00:00 Adrian Prantl aprantl@apple.com 2020-01-16T22:21:17+00:00 urn:sha1:cab81521b5afc2d4295f988aa5f087cbaeefb981 and document the shortcomings of LLDB's partially defined DW_OP_piece handling. This would manifest as "DW_OP_piece for offset foo but top of stack is of size bar". rdar://problem/46262998 Differential Revision: https://reviews.llvm.org/D72880 (cherry picked from commit f55ab6f90b7317a6bb85303a6102702bdae1199e) 2020-02-19T13:20:33+00:00 Adrian Prantl aprantl@apple.com 2020-01-16T22:21:03+00:00 urn:sha1:7751f0c191518b377d9b71bdd17281abec83945a By switching to Scalars that are backed by explicitly-sized APInts we can avoid a bug that increases the buffer reserved for a small piece to the next-largest host integer type. This manifests as "DW_OP_piece for offset foo but top of stack is of size bar". Differential Revision: https://reviews.llvm.org/D72879 (cherry picked from commit 7b0d58e339b271e3b1d9dc14b781b57fa0262e3a) 2020-02-06T09:54:24+00:00 Martin Storsjö martin@martin.st 2020-02-05T20:29:59+00:00 urn:sha1:22633f85bb7d317ff97c86b6ae7817b678777d93 Differential Revision: https://reviews.llvm.org/D74084 (cherry picked from commit 5bbaf543585c54868f8a2bdd9e74edcf395b24b3) 2020-01-27T14:10:11+00:00 shafik syaghmour@apple.com 2020-01-23T22:42:12+00:00 urn:sha1:b5cf892651812003e64c4a8f0dbf81f74a499016 We ran into an assert when debugging clang and performing an expression on a class derived from DeclContext. The assert was indicating we were getting the offsets wrong for RecordDeclBitfields. We were getting both the size and offset of unnamed bit-field members wrong. We could fix this case with a quick change but as I extended the test suite to include more combinations we kept finding more cases that were being handled incorrectly. A fix that handled all the new cases as well as the cases already covered required a refactor of the existing technique. Differential Revision: https://reviews.llvm.org/D72953 (cherry picked from commit fcaf5f6c01a09f23b948afb8c91c4dd951d4525e) 2020-01-15T06:28:49+00:00 Jonas Devlieghere jonas@devlieghere.com 2020-01-15T06:27:00+00:00 urn:sha1:a6faf851f49c7d50e92b16ff9d2e7c02790dd0f8 The 'asynchronously' argument to both GetLLDBCommandsFromIOHandler and GetPythonCommandsFromIOHandler is true for all call sites. This commit simplifies the API by dropping it and giving the baton a default argument. 2020-01-14T17:14:28+00:00 Jonas Devlieghere jonas@devlieghere.com 2020-01-14T17:13:15+00:00 urn:sha1:fd19ffc6a502f8e647696d550abb04a6c8c1b182 llvm_unreachable is marked noreturn so the compiler can assume the code for printing the error message in release builds isn't hit which defeats the purpose. 2020-01-14T14:19:29+00:00 Pavel Labath pavel@labath.sk 2019-12-23T15:31:36+00:00 urn:sha1:4b5bc38802dcc7d2c6d7f5af1eca1755bd0fd9cb These are the last sections not managed by the DWARFContext object. I also introduce separate SectionType enums for dwo section variants, as this is necessary for proper handling of single-file split dwarf.