<?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 basic.ll</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>4681f611 - [hwasan][test] Change -hwasan to -passes=hwasan</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/Instrumentation/HWAddressSanitizer/X86/basic.ll#4681f611</link>
        <description>[hwasan][test] Change -hwasan to -passes=hwasanWith the -enable-new-pm defaulting to true, the two forms have the same effect,but the previous form uses the legacy pass manager syntax which is being phasedout.

            List of files:
            /llvm-project-15.0.7/llvm/test/Instrumentation/HWAddressSanitizer/X86/basic.ll</description>
        <pubDate>Sat, 23 Apr 2022 21:07:31 +0000</pubDate>
        <dc:creator>Fangrui Song &lt;i@maskray.me&gt;</dc:creator>
    </item>
<item>
        <title>96a4167b - [HWASan] Use page aliasing on x86_64.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/Instrumentation/HWAddressSanitizer/X86/basic.ll#96a4167b</link>
        <description>[HWASan] Use page aliasing on x86_64.Userspace page aliasing allows us to use middle pointer bits for tagswithout untagging them before syscalls or accesses.  This should enableeasier experimentation with HWASan on x86_64 platforms.Currently stack, global, and secondary heap tagging are unsupported.Only primary heap allocations get tagged.Note that aliasing mode will not work properly in the presence offork(), since heap memory will be shared between the parent and childprocesses.  This mode is non-ideal; we expect Intel LAM to enable fullHWASan support on x86_64 in the future.Reviewed By: vitalybuka, eugenisDifferential Revision: https://reviews.llvm.org/D98875

            List of files:
            /llvm-project-15.0.7/llvm/test/Instrumentation/HWAddressSanitizer/X86/basic.ll</description>
        <pubDate>Thu, 25 Mar 2021 13:34:25 +0000</pubDate>
        <dc:creator>Matt Morehouse &lt;mascasa@google.com&gt;</dc:creator>
    </item>
<item>
        <title>c8ef98e5 - Revert &quot;[HWASan] Use page aliasing on x86_64.&quot;</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/Instrumentation/HWAddressSanitizer/X86/basic.ll#c8ef98e5</link>
        <description>Revert &quot;[HWASan] Use page aliasing on x86_64.&quot;This reverts commit 63f73c3eb9716256ab8dbb868e16d08a88636cba due tobreakage on aarch64 without TBI.

            List of files:
            /llvm-project-15.0.7/llvm/test/Instrumentation/HWAddressSanitizer/X86/basic.ll</description>
        <pubDate>Wed, 24 Mar 2021 23:17:38 +0000</pubDate>
        <dc:creator>Matt Morehouse &lt;mascasa@google.com&gt;</dc:creator>
    </item>
<item>
        <title>63f73c3e - [HWASan] Use page aliasing on x86_64.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/Instrumentation/HWAddressSanitizer/X86/basic.ll#63f73c3e</link>
        <description>[HWASan] Use page aliasing on x86_64.Userspace page aliasing allows us to use middle pointer bits for tagswithout untagging them before syscalls or accesses.  This should enableeasier experimentation with HWASan on x86_64 platforms.Currently stack, global, and secondary heap tagging are unsupported.Only primary heap allocations get tagged.Note that aliasing mode will not work properly in the presence offork(), since heap memory will be shared between the parent and childprocesses.  This mode is non-ideal; we expect Intel LAM to enable fullHWASan support on x86_64 in the future.Reviewed By: vitalybuka, eugenisDifferential Revision: https://reviews.llvm.org/D98875

            List of files:
            /llvm-project-15.0.7/llvm/test/Instrumentation/HWAddressSanitizer/X86/basic.ll</description>
        <pubDate>Wed, 24 Mar 2021 17:04:37 +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/llvm/test/Instrumentation/HWAddressSanitizer/X86/basic.ll#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/llvm/test/Instrumentation/HWAddressSanitizer/X86/basic.ll</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>83e78414 - [HWASan] Port HWASan to Linux x86-64 (LLVM)</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/Instrumentation/HWAddressSanitizer/X86/basic.ll#83e78414</link>
        <description>[HWASan] Port HWASan to Linux x86-64 (LLVM)Summary:Porting HWASan to Linux x86-64, first of the three patches, LLVM part.The approach is similar to ARM case, trap signal is used to communicatememory tag check failure. int3 instruction is used to generate a signal,access parameters are stored in nop [eax + offset] instruction immediatelyfollowing the int3 one.One notable difference is that x86-64 has to untag the pointer before usedue to the lack of feature comparable to ARM&apos;s TBI (Top Byte Ignore).Reviewers: eugenisSubscribers: kristof.beyls, llvm-commitsDifferential Revision: https://reviews.llvm.org/D44699llvm-svn: 328342

            List of files:
            /llvm-project-15.0.7/llvm/test/Instrumentation/HWAddressSanitizer/X86/basic.ll</description>
        <pubDate>Fri, 23 Mar 2018 17:57:54 +0000</pubDate>
        <dc:creator>Alex Shlyapnikov &lt;alekseys@google.com&gt;</dc:creator>
    </item>
</channel>
</rss>
