<?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 TestQemuAArch64TargetXml.py</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>4cc8f2a0 - [lldb][tests] Automatically call compute_mydir (NFC)</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/test/API/functionalities/gdb_remote_client/TestQemuAArch64TargetXml.py#4cc8f2a0</link>
        <description>[lldb][tests] Automatically call compute_mydir (NFC)Eliminate boilerplate of having each test manually assign to `mydir` by calling`compute_mydir` in lldbtest.py.Differential Revision: https://reviews.llvm.org/D128077

            List of files:
            /llvm-project-15.0.7/lldb/test/API/functionalities/gdb_remote_client/TestQemuAArch64TargetXml.py</description>
        <pubDate>Fri, 17 Jun 2022 00:38:47 +0000</pubDate>
        <dc:creator>Dave Lee &lt;davelee.com@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>33c0f93f - [lldb/test] Move gdb client utils into the packages tree</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/test/API/functionalities/gdb_remote_client/TestQemuAArch64TargetXml.py#33c0f93f</link>
        <description>[lldb/test] Move gdb client utils into the packages treeThis infrastructure has proven proven its worth, so give it a moreprominent place.My immediate motivation for this is the desire to reuse thisinfrastructure for qemu platform testing, but I believe this move makessense independently of that. Moving this code to the packages tree willallow as to add more structure to the gdb client tests -- currently theyare all crammed into the same test folder as that was the only way theycould access this code.I&apos;m splitting the code into two parts while moving it. The first oncecontains just the generic gdb protocol wrappers, while the other onecontains the unit test glue. The reason for that is that for qemutesting, I need to run the gdb code in a separate process, so I willonly be using the first part there.Differential Revision: https://reviews.llvm.org/D113893

            List of files:
            /llvm-project-15.0.7/lldb/test/API/functionalities/gdb_remote_client/TestQemuAArch64TargetXml.py</description>
        <pubDate>Thu, 11 Nov 2021 19:11:14 +0000</pubDate>
        <dc:creator>Pavel Labath &lt;pavel@labath.sk&gt;</dc:creator>
    </item>
<item>
        <title>af3789a1 - [lldb] Improve qemu interop for aarch64</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/test/API/functionalities/gdb_remote_client/TestQemuAArch64TargetXml.py#af3789a1</link>
        <description>[lldb] Improve qemu interop for aarch64qemu calls the &quot;fp&quot; and &quot;lr&quot; registers via their generic names(x29/x30). This mismatch manifested itself as not being able to unwindor display values of some local variables.

            List of files:
            /llvm-project-15.0.7/lldb/test/API/functionalities/gdb_remote_client/TestQemuAArch64TargetXml.py</description>
        <pubDate>Tue, 15 Sep 2020 11:20:09 +0000</pubDate>
        <dc:creator>Pavel Labath &lt;pavel@labath.sk&gt;</dc:creator>
    </item>
</channel>
</rss>
