Project Ortega BCM5719 LLVM https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1 2020-03-03T13:31:05+00:00 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-01-02T19:19:12+00:00 Saleem Abdulrasool compnerd@compnerd.org 2020-01-01T23:01:04+00:00 urn:sha1:abb00753069554c538f3d850897373d093389945 Rather than handling zlib handling manually, use `find_package` from CMake to find zlib properly. Use this to normalize the `LLVM_ENABLE_ZLIB`, `HAVE_ZLIB`, `HAVE_ZLIB_H`. Furthermore, require zlib if `LLVM_ENABLE_ZLIB` is set to `YES`, which requires the distributor to explicitly select whether zlib is enabled or not. This simplifies the CMake handling and usage in the rest of the tooling. This restores 68a235d07f9e7049c7eb0c8091f37e385327ac28, e6c7ed6d2164a0659fd9f6ee44f1375d301e3cad. The problem with the windows bot is a need for clearing the cache. 2020-01-02T16:02:10+00:00 James Henderson jh7370@my.bristol.ac.uk 2020-01-02T15:35:22+00:00 urn:sha1:e406cca5f9a6477c9861717f81c156aa83feeaca This reverts commit 68a235d07f9e7049c7eb0c8091f37e385327ac28. This commit broke the clang-x64-windows-msvc build bot and a follow-up commit did not fix it. Reverting to fix the bot. 2020-01-02T00:36:59+00:00 Saleem Abdulrasool compnerd@compnerd.org 2020-01-01T23:01:04+00:00 urn:sha1:68a235d07f9e7049c7eb0c8091f37e385327ac28 Rather than handling zlib handling manually, use `find_package` from CMake to find zlib properly. Use this to normalize the `LLVM_ENABLE_ZLIB`, `HAVE_ZLIB`, `HAVE_ZLIB_H`. Furthermore, require zlib if `LLVM_ENABLE_ZLIB` is set to `YES`, which requires the distributor to explicitly select whether zlib is enabled or not. This simplifies the CMake handling and usage in the rest of the tooling. 2019-12-10T23:04:45+00:00 Eric Christopher echristo@gmail.com 2019-12-10T23:04:02+00:00 urn:sha1:1d41d1bcdfd70cf8f77bb32e2617392395c299a4 On multiple retry this issue won't duplicate - will revisit with author if duplication works again. This reverts commit c9e0b354e2749ce7ab553974692cb35c8651a869. 2019-12-10T20:29:46+00:00 Eric Christopher echristo@gmail.com 2019-12-10T20:19:30+00:00 urn:sha1:c9e0b354e2749ce7ab553974692cb35c8651a869 This was causing a crash in opt+assert builds on linux and a follow-up message was posted. This reverts commit e81268d03e73aef4f9c7bd8ece8ad02f5b017dcf 2019-12-10T19:16:52+00:00 Jonas Devlieghere jonas@devlieghere.com 2019-12-07T23:28:30+00:00 urn:sha1:e81268d03e73aef4f9c7bd8ece8ad02f5b017dcf When running the test suite with always capture on, a handful of tests are failing because they have multiple targets and therefore multiple GDB remote connections. The current reproducer infrastructure is capable of dealing with that. This patch reworks the GDB remote provider to support multiple GDB remote connections, similar to how the reproducers support shadowing multiple command interpreter inputs. The provider now keeps a list of packet recorders which deal with a single GDB remote connection. During replay we rely on the order of creation to match the number of packets to the GDB remote connection. Differential revision: https://reviews.llvm.org/D71105 2019-09-13T23:14:10+00:00 Jonas Devlieghere jonas@devlieghere.com 2019-09-13T23:14:10+00:00 urn:sha1:ff5225bfb634369e907c889e16cbee36b260362a To support dumping the reproducer's GDB remote packets, we need the (de)serialization logic to live in Utility rather than the GDB remote plugin. This patch renames StreamGDBRemote to GDBRemote and moves the relevant packet code there. Its uses in the GDBRemoteCommunicationHistory and the GDBRemoteCommunicationReplayServer are updated as well. Differential revision: https://reviews.llvm.org/D67523 llvm-svn: 371907 2019-08-21T04:55:56+00:00 Jonas Devlieghere jonas@devlieghere.com 2019-08-21T04:55:56+00:00 urn:sha1:d35b42f20a48d6fd9c1f8fce095c37794d49806c This patch removes the two variant of StringExtractor::GetStringRef that return (non-)const references to std::string. The non-const one was being abused to reinitialize the StringExtractor and its uses are replaced by calls to the copy asignment operator. The const variant was refactored to return an actual llvm::StringRef. llvm-svn: 369493 2019-08-20T09:24:20+00:00 Jan Kratochvil jan.kratochvil@redhat.com 2019-08-20T09:24:20+00:00 urn:sha1:f9d90bc5f690de43cbfd8bd15f6f3d3e01471615 I find as a good cleanup to drop the Compile method. As I do not find TIMTOWTDI as an advantage and there is already constructor parameter to compile the regex. Differential Revision: https://reviews.llvm.org/D66392 llvm-svn: 369352