<?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 longjmp.cpp</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>c4992bf5 - [NFC][sanitizer] Remove calls to __asan_get_current_fake_stack</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/asan/TestCases/longjmp.cpp#c4992bf5</link>
        <description>[NFC][sanitizer] Remove calls to __asan_get_current_fake_stackUnnecessary with -fsanitize-address-use-after-return=never.for issue: https://github.com/google/sanitizers/issues/1394Reviewed By: vitalybukaDifferential Revision: https://reviews.llvm.org/D104154

            List of files:
            /llvm-project-15.0.7/compiler-rt/test/asan/TestCases/longjmp.cpp</description>
        <pubDate>Wed, 16 Jun 2021 01:26:31 +0000</pubDate>
        <dc:creator>Kevin Athey &lt;kda@google.com&gt;</dc:creator>
    </item>
<item>
        <title>ba1202a1 - [PowerPC] Restore stack ptr from base ptr when available</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/asan/TestCases/longjmp.cpp#ba1202a1</link>
        <description>[PowerPC] Restore stack ptr from base ptr when availableOn subtargets that have a red zone, we will copy the stack pointer to the basepointer in the prologue prior to updating the stack pointer. There are no otherupdates to the base pointer after that. This suggests that we should be able torestore the stack pointer from the base pointer rather than loading it from theback chain or adding the frame size back to either the stack pointer or theframe pointer.This came about because functions that call setjmp need to restore the SP fromthe FP because the back chain might have been clobbered(see https://reviews.llvm.org/D92906). However, if the stack is realigned, therestored SP might be incorrect (which is what caused the failures in the twoASan test cases).This patch was tested quite extensivelly both with sanitizer runtimes andgeneral code.Differential revision: https://reviews.llvm.org/D93327

            List of files:
            /llvm-project-15.0.7/compiler-rt/test/asan/TestCases/longjmp.cpp</description>
        <pubDate>Tue, 22 Dec 2020 11:43:33 +0000</pubDate>
        <dc:creator>Nemanja Ivanovic &lt;nemanja.i.ibm@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>eed0b9ac - [PowerPC] Temporarily disable asan longjmp tests</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/asan/TestCases/longjmp.cpp#eed0b9ac</link>
        <description>[PowerPC] Temporarily disable asan longjmp testsCommit bfdc19e77868b849b5c636bf0512970264aef571 seems to have brokensome PPC bots with a couple of asan test cases. Disable those testcases for now until I can resolve the issue.

            List of files:
            /llvm-project-15.0.7/compiler-rt/test/asan/TestCases/longjmp.cpp</description>
        <pubDate>Tue, 15 Dec 2020 00:07:45 +0000</pubDate>
        <dc:creator>Nemanja Ivanovic &lt;nemanja.i.ibm@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>673dc3d4 - compiler-rt: Rename cc files below test/asan to cpp</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/asan/TestCases/longjmp.cpp#673dc3d4</link>
        <description>compiler-rt: Rename cc files below test/asan to cppSee r367803 and similar other changes.llvm-svn: 367887

            List of files:
            /llvm-project-15.0.7/compiler-rt/test/asan/TestCases/longjmp.cpp</description>
        <pubDate>Mon, 05 Aug 2019 16:48:12 +0000</pubDate>
        <dc:creator>Nico Weber &lt;nicolasweber@gmx.de&gt;</dc:creator>
    </item>
</channel>
</rss>
