<?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 deep-recursion.c</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>21f72c05 - [hwasan] Add __hwasan_add_frame_record to the hwasan interface</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/deep-recursion.c#21f72c05</link>
        <description>[hwasan] Add __hwasan_add_frame_record to the hwasan interfaceHwasan includes instructions in the prologue that mix the PC and SP and storeit into the stack ring buffer stored at __hwasan_tls. This is a thread_localglobal exposed from the hwasan runtime. However, if TLS-mechanisms or thehwasan runtime haven&apos;t been setup yet, it will be invalid to access __hwasan_tls.This is the case for Fuchsia where we instrument libc, so some functions thatare instrumented but can run before hwasan initialization will incorrectlyaccess this global. Additionally, libc cannot have any TLS variables, so wecannot weakly define __hwasan_tls until the runtime is loaded.A way we can work around this is by moving the instructions into a hwasanfunction that does the store into the ring buffer and creating a weak definitionof that function locally in libc. This way __hwasan_tls will not actually bereferenced. This is not our long-term solution, but this will allow us to rollout hwasan in the meantime.This patch includes:- A new llvm flag for choosing to emit a libcall rather than instructions in the  prologue (off by default)- The libcall for storing into the ringbuffer (__hwasan_add_frame_record)Differential Revision: https://reviews.llvm.org/D128387

            List of files:
            /llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/deep-recursion.c</description>
        <pubDate>Wed, 13 Jul 2022 22:07:59 +0000</pubDate>
        <dc:creator>Leonard Chan &lt;leonardchan@google.com&gt;</dc:creator>
    </item>
<item>
        <title>d843d5c8 - Revert &quot;[hwasan] Add __hwasan_record_frame_record to the hwasan interface&quot;</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/deep-recursion.c#d843d5c8</link>
        <description>Revert &quot;[hwasan] Add __hwasan_record_frame_record to the hwasan interface&quot;This reverts commit 4956620387ee45a48a394853a47ddd65195c4cc6.This broke a sanitizer builder: https://lab.llvm.org/buildbot/#/builders/77/builds/19597

            List of files:
            /llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/deep-recursion.c</description>
        <pubDate>Wed, 13 Jul 2022 22:06:07 +0000</pubDate>
        <dc:creator>Leonard Chan &lt;leonardchan@google.com&gt;</dc:creator>
    </item>
<item>
        <title>49566203 - [hwasan] Add __hwasan_record_frame_record to the hwasan interface</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/deep-recursion.c#49566203</link>
        <description>[hwasan] Add __hwasan_record_frame_record to the hwasan interfaceHwasan includes instructions in the prologue that mix the PC and SP and storeit into the stack ring buffer stored at __hwasan_tls. This is a thread_localglobal exposed from the hwasan runtime. However, if TLS-mechanisms or thehwasan runtime haven&apos;t been setup yet, it will be invalid to access __hwasan_tls.This is the case for Fuchsia where we instrument libc, so some functions thatare instrumented but can run before hwasan initialization will incorrectlyaccess this global. Additionally, libc cannot have any TLS variables, so wecannot weakly define __hwasan_tls until the runtime is loaded.A way we can work around this is by moving the instructions into a hwasanfunction that does the store into the ring buffer and creating a weak definitionof that function locally in libc. This way __hwasan_tls will not actually bereferenced. This is not our long-term solution, but this will allow us to rollout hwasan in the meantime.This patch includes:- A new llvm flag for choosing to emit a libcall rather than instructions in the  prologue (off by default)- The libcall for storing into the ringbuffer (__hwasan_record_frame_record)Differential Revision: https://reviews.llvm.org/D128387

            List of files:
            /llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/deep-recursion.c</description>
        <pubDate>Wed, 06 Jul 2022 21:47:43 +0000</pubDate>
        <dc:creator>leonardchan &lt;leonardchan@google.com&gt;</dc:creator>
    </item>
<item>
        <title>0867edfc - [HWASan] Add basic stack tagging support for LAM.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/deep-recursion.c#0867edfc</link>
        <description>[HWASan] Add basic stack tagging support for LAM.Adds the basic instrumentation needed for stack tagging.Currently does not support stack short granules or TLS stack histories,since a different code path is followed for the callback instrumentationwe use.We may simply wait to support these two features until we switch toa custom calling convention.Patch By: xiangzhangllvm, morehouseReviewed By: vitalybukaDifferential Revision: https://reviews.llvm.org/D102901

            List of files:
            /llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/deep-recursion.c</description>
        <pubDate>Fri, 11 Jun 2021 15:19:36 +0000</pubDate>
        <dc:creator>Matt Morehouse &lt;mascasa@google.com&gt;</dc:creator>
    </item>
<item>
        <title>772851ca - [HWASan] Disable stack, globals and force callbacks for x86_64.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/deep-recursion.c#772851ca</link>
        <description>[HWASan] Disable stack, globals and force callbacks for x86_64.Subsequent patches will implement page-aliasing mode for x86_64, whichwill initially only work for the primary heap allocator.  We forcecallback instrumentation to simplify the initial aliasingimplementation.Reviewed By: vitalybuka, eugenisDifferential Revision: https://reviews.llvm.org/D98069

            List of files:
            /llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/deep-recursion.c</description>
        <pubDate>Mon, 22 Mar 2021 15:01:48 +0000</pubDate>
        <dc:creator>Matt Morehouse &lt;mascasa@google.com&gt;</dc:creator>
    </item>
<item>
        <title>a53bb3ac - Fix typo in test cases as well.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/deep-recursion.c#a53bb3ac</link>
        <description>Fix typo in test cases as well.llvm-svn: 349255

            List of files:
            /llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/deep-recursion.c</description>
        <pubDate>Sat, 15 Dec 2018 07:08:04 +0000</pubDate>
        <dc:creator>Peter Collingbourne &lt;peter@pcc.me.uk&gt;</dc:creator>
    </item>
<item>
        <title>090f0f95 - [hwasan] Record and display stack history in stack-based reports.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/deep-recursion.c#090f0f95</link>
        <description>[hwasan] Record and display stack history in stack-based reports.Summary:Display a list of recent stack frames (not a stack trace!) whentag-mismatch is detected on a stack address.The implementation uses alignment tricks to get both the address ofthe history buffer, and the base address of the shadow with a single8-byte load. See the comment in hwasan_thread_list.h for moredetails.Developed in collaboration with Kostya Serebryany.Reviewers: kccSubscribers: srhines, kubamracek, mgorny, hiraditya, jfb, llvm-commitsDifferential Revision: https://reviews.llvm.org/D52249llvm-svn: 342923

            List of files:
            /llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/deep-recursion.c</description>
        <pubDate>Mon, 24 Sep 2018 23:03:34 +0000</pubDate>
        <dc:creator>Evgeniy Stepanov &lt;eugeni.stepanov@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>9043e17e - [hwasan] Record and display stack history in stack-based reports.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/deep-recursion.c#9043e17e</link>
        <description>[hwasan] Record and display stack history in stack-based reports.Summary:Display a list of recent stack frames (not a stack trace!) whentag-mismatch is detected on a stack address.The implementation uses alignment tricks to get both the address ofthe history buffer, and the base address of the shadow with a single8-byte load. See the comment in hwasan_thread_list.h for moredetails.Developed in collaboration with Kostya Serebryany.Reviewers: kccSubscribers: srhines, kubamracek, mgorny, hiraditya, jfb, llvm-commitsDifferential Revision: https://reviews.llvm.org/D52249llvm-svn: 342921

            List of files:
            /llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/deep-recursion.c</description>
        <pubDate>Mon, 24 Sep 2018 21:38:42 +0000</pubDate>
        <dc:creator>Evgeniy Stepanov &lt;eugeni.stepanov@gmail.com&gt;</dc:creator>
    </item>
</channel>
</rss>
