<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm5719-llvm/compiler-rt/test, 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-06-23T22:43:11+00:00</updated>
<entry>
<title>[compiler-rt] Reduce the number of threads in gcov test to avoid failure</title>
<updated>2020-06-23T22:43:11+00:00</updated>
<author>
<name>Calixte Denizet</name>
<email>calixte.denizet@gmail.com</email>
</author>
<published>2020-05-08T09:04:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=5ccc104c206c02e712dec68cc0daef6379f51861'/>
<id>urn:sha1:5ccc104c206c02e712dec68cc0daef6379f51861</id>
<content type='text'>
Summary:
Patch in D78477 introduced a new test for gcov and this test is failing on arm:
 - http://lab.llvm.org:8011/builders/clang-cmake-thumbv7-full-sh/builds/4752/steps/ninja%20check%202/logs/stdio
  - http://lab.llvm.org:8011/builders/clang-cmake-armv7-full/builds/10501/steps/ninja%20check%202/logs/stdio
So try to fix it in reducing the number of threads.

Reviewers: marco-c

Reviewed By: marco-c

Subscribers: dberris, kristof.beyls, #sanitizers, serge-sans-paille, sylvestre.ledru

Tags: #sanitizers

Differential Revision: https://reviews.llvm.org/D79621

(cherry picked from commit 0da37bedc2667da371eda30595a06210595881d0)
</content>
</entry>
<entry>
<title>[profile] Don't crash when forking in several threads</title>
<updated>2020-05-07T18:18:56+00:00</updated>
<author>
<name>Calixte Denizet</name>
<email>calixte.denizet@gmail.com</email>
</author>
<published>2020-04-20T08:50:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=f082d91801645e999aa8b1072392f945405eafc5'/>
<id>urn:sha1:f082d91801645e999aa8b1072392f945405eafc5</id>
<content type='text'>
Summary:
When forking in several threads, the counters were written out in using the same global static variables (see GCDAProfiling.c): that leads to crashes.
So when there is a fork, the counters are resetted in the child process and they will be dumped at exit using the interprocess file locking.
When there is an exec, the counters are written out and in case of failures they're resetted.

Reviewers: jfb, vsk, marco-c, serge-sans-paille

Reviewed By: marco-c, serge-sans-paille

Subscribers: llvm-commits, serge-sans-paille, dmajor, cfe-commits, hiraditya, dexonsmith, #sanitizers, marco-c, sylvestre.ledru

Tags: #sanitizers, #clang, #llvm

Differential Revision: https://reviews.llvm.org/D78477

(cherry picked from commit bec223a9bc4eb9747993ee9a4c1aa135c32123e6)
</content>
</entry>
<entry>
<title>Revert abb00753 "build: reduce CMake handling for zlib" (PR44780)</title>
<updated>2020-03-03T13:31:05+00:00</updated>
<author>
<name>Hans Wennborg</name>
<email>hans@chromium.org</email>
</author>
<published>2020-03-03T08:45:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=5f9211bc46fa1a8d1db3a2bc27c2b115cd617795'/>
<id>urn:sha1:5f9211bc46fa1a8d1db3a2bc27c2b115cd617795</id>
<content type='text'>
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)
</content>
</entry>
<entry>
<title>[profile] Support merge pool size &gt;= 10</title>
<updated>2020-01-12T08:27:18+00:00</updated>
<author>
<name>Fangrui Song</name>
<email>maskray@google.com</email>
</author>
<published>2020-01-12T08:24:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=c5b94ea265133a4a28006929643155fc8fbeafe6'/>
<id>urn:sha1:c5b94ea265133a4a28006929643155fc8fbeafe6</id>
<content type='text'>
The executable acquires an advisory record lock (`fcntl(fd, F_SETLKW, *)`) on a profile file.
Merge pool size &gt;= 10 may be beneficial when the concurrency is large.

Also fix a small problem about snprintf. It can cause the filename to be truncated after %m.

Reviewed By: davidxl

Differential Revision: https://reviews.llvm.org/D71970
</content>
</entry>
<entry>
<title>[cfi][test] cross-dso/stats.cpp: don't assume the order of static constructors</title>
<updated>2020-01-08T23:50:51+00:00</updated>
<author>
<name>Fangrui Song</name>
<email>maskray@google.com</email>
</author>
<published>2020-01-08T23:44:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=7f1026a7520eb3d7e99da77f6738deb72de17980'/>
<id>urn:sha1:7f1026a7520eb3d7e99da77f6738deb72de17980</id>
<content type='text'>
__sanitizer_stat_init is called for the executable first, then the
shared object. In WriterModuleReport(), the information for the shared
object will be recorded first. It'd be nice to get rid of the order
requirement of static constructors. (This should make .ctors platforms
work.)
</content>
</entry>
<entry>
<title>[msan] Fix underflow in qsort interceptor.</title>
<updated>2020-01-07T00:12:52+00:00</updated>
<author>
<name>Evgenii Stepanov</name>
<email>eugenis@google.com</email>
</author>
<published>2020-01-07T00:12:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=7ba4595c86be88bf9ebb7261ba49ed4626e5f585'/>
<id>urn:sha1:7ba4595c86be88bf9ebb7261ba49ed4626e5f585</id>
<content type='text'>
</content>
</entry>
<entry>
<title>[msan] Check qsort input.</title>
<updated>2020-01-06T23:07:02+00:00</updated>
<author>
<name>Evgenii Stepanov</name>
<email>eugenis@google.com</email>
</author>
<published>2019-12-20T20:07:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=b5e7f95cfbeb28ff8b966a2b7e38a03f32410030'/>
<id>urn:sha1:b5e7f95cfbeb28ff8b966a2b7e38a03f32410030</id>
<content type='text'>
Summary:
Qsort interceptor suppresses all checks by unpoisoning the data in the
wrapper of a comparator function, and then unpoisoning the output array
as well.

This change adds an explicit run of the comparator on all elements of
the input array to catch any sanitizer bugs.

Reviewers: vitalybuka

Subscribers: #sanitizers, llvm-commits

Tags: #sanitizers, #llvm

Differential Revision: https://reviews.llvm.org/D71780
</content>
</entry>
<entry>
<title>build: reduce CMake handling for zlib</title>
<updated>2020-01-02T19:19:12+00:00</updated>
<author>
<name>Saleem Abdulrasool</name>
<email>compnerd@compnerd.org</email>
</author>
<published>2020-01-01T23:01:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=abb00753069554c538f3d850897373d093389945'/>
<id>urn:sha1:abb00753069554c538f3d850897373d093389945</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Revert "build: reduce CMake handling for zlib"</title>
<updated>2020-01-02T16:02:10+00:00</updated>
<author>
<name>James Henderson</name>
<email>jh7370@my.bristol.ac.uk</email>
</author>
<published>2020-01-02T15:35:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=e406cca5f9a6477c9861717f81c156aa83feeaca'/>
<id>urn:sha1:e406cca5f9a6477c9861717f81c156aa83feeaca</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>build: reduce CMake handling for zlib</title>
<updated>2020-01-02T00:36:59+00:00</updated>
<author>
<name>Saleem Abdulrasool</name>
<email>compnerd@compnerd.org</email>
</author>
<published>2020-01-01T23:01:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=68a235d07f9e7049c7eb0c8091f37e385327ac28'/>
<id>urn:sha1:68a235d07f9e7049c7eb0c8091f37e385327ac28</id>
<content type='text'>
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.
</content>
</entry>
</feed>
