Project Ortega BCM5719 LLVM https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1 2019-12-24T19:34:58+00:00 2019-12-24T19:34:58+00:00 Kamil Rytarowski n54@gmx.com 2019-12-24T19:34:58+00:00 urn:sha1:4b8232d4f0bf5fd9f11ebef2b0f9e8e15f130fb3 Enable compat support for now legacy PT_LWPINFO. Support PT_LWPSTATUS and PT_LWPNEXT. 2019-12-04T22:18:52+00:00 Max Moroz mmoroz@chromium.org 2019-12-04T21:24:59+00:00 urn:sha1:a44ef027ebca1598892ea9b104d6189aeb3bc2f0 Summary: Some versions of memcpy mark pointer arguments as __nonnull, that triggers UBSan errors even when the length passed is 0. Reviewers: manojgupta, metzman Subscribers: dberris, #sanitizers, llvm-commits Tags: #sanitizers, #llvm Differential Revision: https://reviews.llvm.org/D71031 [compiler-rt] FDP: assert that num_bytes_to_consume == 0 when size == 0. 2019-12-04T18:35:14+00:00 Vedant Kumar vsk@apple.com 2019-12-04T18:35:14+00:00 urn:sha1:f208b70fbc4dee78067b3c5bd6cb92aa3ba58a1e This reverts commit e18531595bba495946aa52c0a16b9f9238cff8bc. On Windows, there is an error: http://lab.llvm.org:8011/builders/sanitizer-windows/builds/54963/steps/stage%201%20check/logs/stdio error: C:\b\slave\sanitizer-windows\build\stage1\projects\compiler-rt\test\profile\Profile-x86_64\Output\instrprof-merging.cpp.tmp.v1.o: Failed to load coverage: Malformed coverage data 2019-12-04T18:10:55+00:00 Vedant Kumar vsk@apple.com 2019-10-21T18:48:38+00:00 urn:sha1:e18531595bba495946aa52c0a16b9f9238cff8bc Revise the coverage mapping format to reduce binary size by: 1. Naming function records and marking them `linkonce_odr`, and 2. Compressing filenames. This shrinks the size of llc's coverage segment by 82% (334MB -> 62MB) and speeds up end-to-end single-threaded report generation by 10%. For reference the compressed name data in llc is 81MB (__llvm_prf_names). Rationale for changes to the format: - With the current format, most coverage function records are discarded. E.g., more than 97% of the records in llc are *duplicate* placeholders for functions visible-but-not-used in TUs. Placeholders *are* used to show under-covered functions, but duplicate placeholders waste space. - We reached general consensus about giving (1) a try at the 2017 code coverage BoF [1]. The thinking was that using `linkonce_odr` to merge duplicates is simpler than alternatives like teaching build systems about a coverage-aware database/module/etc on the side. - Revising the format is expensive due to the backwards compatibility requirement, so we might as well compress filenames while we're at it. This shrinks the encoded filenames in llc by 86% (12MB -> 1.6MB). See CoverageMappingFormat.rst for the details on what exactly has changed. Fixes PR34533 [2], hopefully. [1] http://lists.llvm.org/pipermail/llvm-dev/2017-October/118428.html [2] https://bugs.llvm.org/show_bug.cgi?id=34533 Differential Revision: https://reviews.llvm.org/D69471 2019-11-22T22:09:46+00:00 Petr Hosek phosek@google.com 2019-11-22T20:09:15+00:00 urn:sha1:f35032e03d9263b1d2a8ac2e675fc94cb43b608b This header fragment is useful on its own for any consumer that wants to use custom instruction profile runtime with the LLVM instrumentation. The concrete use case is in Fuchsia's kernel where we want to use instruction profile instrumentation, but we cannot use the compiler-rt runtime because it's not designed for use in the kernel environment. This change allows installing this header as part of compiler-rt. Differential Revision: https://reviews.llvm.org/D64532 2019-11-22T20:00:23+00:00 Petr Hosek phosek@google.com 2019-11-22T20:00:23+00:00 urn:sha1:262b10ba1f9db4d00f43bcb1d8c1e557dced3bcd This reverts commit f11bc1776fd2815b60e0b1ed97be00b517348162 since it's failing to build on some bots. 2019-11-22T19:52:50+00:00 Petr Hosek phosek@google.com 2019-11-22T03:39:51+00:00 urn:sha1:f11bc1776fd2815b60e0b1ed97be00b517348162 This header fragment is useful on its own for any consumer that wants to use custom instruction profile runtime with the LLVM instrumentation. The concrete use case is in Fuchsia's kernel where we want to use instruction profile instrumentation, but we cannot use the compiler-rt runtime because it's not designed for use in the kernel environment. This change allows installing this header as part of compiler-rt. Differential Revision: https://reviews.llvm.org/D64532 2019-11-03T15:22:02+00:00 Kamil Rytarowski n54@gmx.com 2019-11-03T15:17:26+00:00 urn:sha1:01f91c3526efe58aa035c7f27bef817195c7d26c Document the minimal version supported as 9.0 and add compat code for renamed syscalls after 9.0. 2019-10-31T20:54:46+00:00 Evgenii Stepanov eugenis@google.com 2019-10-19T00:17:48+00:00 urn:sha1:13e04607f75bdf0e4de08b6f240501c15e8891f1 Summary: Sometimes an allocation stack trace is not very informative. Provide a way to replace it with a stack trace of the user's choice. Reviewers: pcc, kcc Subscribers: #sanitizers, llvm-commits Tags: #sanitizers, #llvm Differential Revision: https://reviews.llvm.org/D69208 2019-09-13T08:22:58+00:00 Pierre Gousseau pierregousseau14@gmail.com 2019-09-13T08:22:58+00:00 urn:sha1:1ae9e6918d94ec0e296c7753cd3f1a7c22cb3153 This is to document __ubsan_default_options(). Reviewed By: vitalybuka Differential Revision: https://reviews.llvm.org/D67503 llvm-svn: 371822