<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in tsan_test.cpp</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>ca50840b - [Sanitizer][Darwin] Cleanup MaybeReexec() function and usage</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/lib/tsan/tests/rtl/tsan_test.cpp#ca50840b</link>
        <description>[Sanitizer][Darwin] Cleanup MaybeReexec() function and usageWhile investigating another issue, I noticed that `MaybeReexec()` neveractually &quot;re-executes via `execv()`&quot; anymore.  `DyldNeedsEnvVariable()`only returned true on macOS 10.10 and below.Usually, I try to avoid &quot;unnecessary&quot; cleanups (it&apos;s hard to be certainthat there truly is no fallout), but I decided to do this one because:* I initially tricked myself into thinking that `MaybeReexec()` was  relevant to my original investigation (instead of being dead code).* The deleted code itself is quite complicated.* Over time a few other things were mushed into `MaybeReexec()`:  initializing `MonotonicNanoTime()`, verifying interceptors are  working, and stripping the `DYLD_INSERT_LIBRARIES` env var to avoid  problems when forking.* This platform-specific thing leaked into `sanitizer_common.h`.* The `ReexecDisabled()` config nob relies on the &quot;strong overrides weak  pattern&quot;, which is now problematic and can be completely removed.* `ReexecDisabled()` actually hid another issue with interceptors not  working in unit tests.  I added an explicit `verify_interceptors`  (defaults to `true`) option instead.Differential Revision: https://reviews.llvm.org/D129157

            List of files:
            /llvm-project-15.0.7/compiler-rt/lib/tsan/tests/rtl/tsan_test.cpp</description>
        <pubDate>Fri, 01 Jul 2022 18:05:40 +0000</pubDate>
        <dc:creator>Julian Lettner &lt;julian.lettner@apple.com&gt;</dc:creator>
    </item>
<item>
        <title>7789c9af - Revert &quot;[Sanitizer][Darwin] Cleanup MaybeReexec() function and usage&quot;</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/lib/tsan/tests/rtl/tsan_test.cpp#7789c9af</link>
        <description>Revert &quot;[Sanitizer][Darwin] Cleanup MaybeReexec() function and usage&quot;Many tests for the `UBSan-Standalone-iossim-x86_64` fail with this.Reverting so I can investigate.This reverts commit 0a9667b0f56b1b450abd02f74c6175bea54f832e.

            List of files:
            /llvm-project-15.0.7/compiler-rt/lib/tsan/tests/rtl/tsan_test.cpp</description>
        <pubDate>Fri, 08 Jul 2022 00:26:19 +0000</pubDate>
        <dc:creator>Julian Lettner &lt;julian.lettner@apple.com&gt;</dc:creator>
    </item>
<item>
        <title>0a9667b0 - [Sanitizer][Darwin] Cleanup MaybeReexec() function and usage</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/lib/tsan/tests/rtl/tsan_test.cpp#0a9667b0</link>
        <description>[Sanitizer][Darwin] Cleanup MaybeReexec() function and usageWhile investigating another issue, I noticed that `MaybeReexec()` neveractually &quot;re-executes via `execv()`&quot; anymore.  `DyldNeedsEnvVariable()`only returned true on macOS 10.10 and below.Usually, I try to avoid &quot;unnecessary&quot; cleanups (it&apos;s hard to be certainthat there truly is no fallout), but I decided to do this one because:* I initially tricked myself into thinking that `MaybeReexec()` was  relevant to my original investigation (instead of being dead code).* The deleted code itself is quite complicated.* Over time a few other things were mushed into `MaybeReexec()`:  initializing `MonotonicNanoTime()`, verifying interceptors are  working, and stripping the `DYLD_INSERT_LIBRARIES` env var to avoid  problems when forking.* This platform-specific thing leaked into `sanitizer_common.h`.* The `ReexecDisabled()` config nob relies on the &quot;strong overrides weak  pattern&quot;, which is now problematic and can be completely removed.* `ReexecDisabled()` actually hid another issue with interceptors not  working in unit tests.  I added an explicit `verify_interceptors`  (defaults to `true`) option instead.Differential Revision: https://reviews.llvm.org/D129157

            List of files:
            /llvm-project-15.0.7/compiler-rt/lib/tsan/tests/rtl/tsan_test.cpp</description>
        <pubDate>Fri, 01 Jul 2022 18:05:40 +0000</pubDate>
        <dc:creator>Julian Lettner &lt;julian.lettner@apple.com&gt;</dc:creator>
    </item>
<item>
        <title>a61c8e1e - tsan: for unittests, change to use test fixtures to clear racy stacks</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/lib/tsan/tests/rtl/tsan_test.cpp#a61c8e1e</link>
        <description>tsan: for unittests, change to use test fixtures to clear racy stacksAfter cd0a5889d71, unittest would run in shard mode where many testsshare a single process. Need to clear some global state to make the testresults stable.Reviewed By: thetruestblue, rsundahlDifferential Revision: https://reviews.llvm.org/D124591

            List of files:
            /llvm-project-15.0.7/compiler-rt/lib/tsan/tests/rtl/tsan_test.cpp</description>
        <pubDate>Tue, 03 May 2022 17:13:15 +0000</pubDate>
        <dc:creator>Yuanfang Chen &lt;yuanfang.chen@sony.com&gt;</dc:creator>
    </item>
<item>
        <title>5de29a4b - compiler-rt: Rename .cc file in lib/tsan/tests/{rtl,unit} to .cpp</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/lib/tsan/tests/rtl/tsan_test.cpp#5de29a4b</link>
        <description>compiler-rt: Rename .cc file in lib/tsan/tests/{rtl,unit} to .cppLike r367463, but for tsan/tests/{rtl,unit}.llvm-svn: 367566

            List of files:
            /llvm-project-15.0.7/compiler-rt/lib/tsan/tests/rtl/tsan_test.cpp</description>
        <pubDate>Thu, 01 Aug 2019 14:26:37 +0000</pubDate>
        <dc:creator>Nico Weber &lt;nicolasweber@gmx.de&gt;</dc:creator>
    </item>
</channel>
</rss>
