<?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 vararg-kernel.ll</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>41d5033e - [IR] Enable opaque pointers by default</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/Instrumentation/MemorySanitizer/SystemZ/vararg-kernel.ll#41d5033e</link>
        <description>[IR] Enable opaque pointers by defaultThis enabled opaque pointers by default in LLVM. The effect of thisis twofold:* If IR that contains *neither* explicit ptr nor %T* types is passed  to tools, we will now use opaque pointer mode, unless  -opaque-pointers=0 has been explicitly passed.* Users of LLVM as a library will now default to opaque pointers.  It is possible to opt-out by calling setOpaquePointers(false) on  LLVMContext.A cmake option to toggle this default will not be provided. Frontendsor other tools that want to (temporarily) keep using typed pointersshould disable opaque pointers via LLVMContext.Differential Revision: https://reviews.llvm.org/D126689

            List of files:
            /llvm-project-15.0.7/llvm/test/Instrumentation/MemorySanitizer/SystemZ/vararg-kernel.ll</description>
        <pubDate>Tue, 31 May 2022 09:58:35 +0000</pubDate>
        <dc:creator>Nikita Popov &lt;npopov@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>3ff17b05 - [msan][test] Remove legacy PM style opt -foo tests</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/Instrumentation/MemorySanitizer/SystemZ/vararg-kernel.ll#3ff17b05</link>
        <description>[msan][test] Remove legacy PM style opt -foo tests

            List of files:
            /llvm-project-15.0.7/llvm/test/Instrumentation/MemorySanitizer/SystemZ/vararg-kernel.ll</description>
        <pubDate>Sat, 16 Apr 2022 04:07:50 +0000</pubDate>
        <dc:creator>Fangrui Song &lt;i@maskray.me&gt;</dc:creator>
    </item>
<item>
        <title>8224c504 - For some tests targeting SystemZ, -march=z13 ---&gt; -mcpu=z13</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/Instrumentation/MemorySanitizer/SystemZ/vararg-kernel.ll#8224c504</link>
        <description>For some tests targeting SystemZ, -march=z13 ---&gt; -mcpu=z13z13 is not a target. It is a CPU.

            List of files:
            /llvm-project-15.0.7/llvm/test/Instrumentation/MemorySanitizer/SystemZ/vararg-kernel.ll</description>
        <pubDate>Thu, 30 Jul 2020 01:34:32 +0000</pubDate>
        <dc:creator>Yuanfang Chen &lt;yuanfang.chen@sony.com&gt;</dc:creator>
    </item>
<item>
        <title>0b0bb196 - [llvm] Fix yet more missing FileCheck colons</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/Instrumentation/MemorySanitizer/SystemZ/vararg-kernel.ll#0b0bb196</link>
        <description>[llvm] Fix yet more missing FileCheck colons

            List of files:
            /llvm-project-15.0.7/llvm/test/Instrumentation/MemorySanitizer/SystemZ/vararg-kernel.ll</description>
        <pubDate>Mon, 13 Apr 2020 16:21:01 +0000</pubDate>
        <dc:creator>Jon Roelofs &lt;jroelofs@jroelofs.com&gt;</dc:creator>
    </item>
<item>
        <title>3bc439bd - [MSan] Add instrumentation for SystemZ</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/Instrumentation/MemorySanitizer/SystemZ/vararg-kernel.ll#3bc439bd</link>
        <description>[MSan] Add instrumentation for SystemZSummary:This patch establishes memory layout and adds instrumentation. It doesnot add runtime support and does not enable MSan, which will be doneseparately.Memory layout is based on PPC64, with the exception that XorMaskis not used - low and high memory addresses are chosen in a way thatapplying AndMask to low and high memory produces non-overlappingresults.VarArgHelper is based on AMD64. It might be tempting to share somecode between the two implementations, but we need to keep in mind thatall the ABI similarities are coincidental, and therefore any suchsharing might backfire.copyRegSaveArea() indiscriminately copies the entire register save areashadow, however, fragments thereof not filled by the correspondingvisitCallSite() invocation contain irrelevant data. Whether or not thiscan lead to practical problems is unclear, hence a simple TODO comment.Note that the behavior of the related copyOverflowArea() is correct: itcopies only the vararg-related fragment of the overflow area shadow.VarArgHelper test is based on the AArch64 one.s390x ABI requires that arguments are zero-extended to 64 bits. This isparticularly important for __msan_maybe_warning_*() and__msan_maybe_store_origin_*() shadow and origin arguments, since nonzeroed upper parts thereof confuse these functions. Therefore, add ZExtattribute to the corresponding parameters.Add ZExt attribute checks to msan-basic.ll. Since with-msan-instrumentation-with-call-threshold=0 instrumentation looks quitedifferent, introduce the new CHECK-CALLS check prefix.Reviewers: eugenis, vitalybuka, uweigand, jonpaReviewed By: eugenisSubscribers: kristof.beyls, hiraditya, danielkiss, llvm-commits, stefansf, Andreas-KrebbelTags: #llvmDifferential Revision: https://reviews.llvm.org/D76624

            List of files:
            /llvm-project-15.0.7/llvm/test/Instrumentation/MemorySanitizer/SystemZ/vararg-kernel.ll</description>
        <pubDate>Thu, 09 Apr 2020 20:06:01 +0000</pubDate>
        <dc:creator>Ilya Leoshkevich &lt;iii@linux.ibm.com&gt;</dc:creator>
    </item>
</channel>
</rss>
