<?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 types-recursive-struct.ll</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>4ab3041a - Revert &quot;[NFC] remove explicit default value for strboolattr attribute in tests&quot;</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-recursive-struct.ll#4ab3041a</link>
        <description>Revert &quot;[NFC] remove explicit default value for strboolattr attribute in tests&quot;This reverts commit bda6e5bee04c75b1f1332b4fd1ac4e8ef6c3c247.See https://lab.llvm.org/buildbot/#/builders/109/builds/15424 for instance

            List of files:
            /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-recursive-struct.ll</description>
        <pubDate>Mon, 24 May 2021 17:43:40 +0000</pubDate>
        <dc:creator>serge-sans-paille &lt;sguelton@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>bda6e5be - [NFC] remove explicit default value for strboolattr attribute in tests</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-recursive-struct.ll#bda6e5be</link>
        <description>[NFC] remove explicit default value for strboolattr attribute in testsSince d6de1e1a71406c75a4ea4d5a2fe84289f07ea3a1, no attributes is quivalent tosetting attribute to false.This is a preliminary commit for https://reviews.llvm.org/D99080

            List of files:
            /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-recursive-struct.ll</description>
        <pubDate>Sun, 23 May 2021 11:19:23 +0000</pubDate>
        <dc:creator>serge-sans-paille &lt;sguelton@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>cbf25fbe - Revert &quot;[CodeGen] [WinException] Only produce handler data at the end of the function if needed&quot;</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-recursive-struct.ll#cbf25fbe</link>
        <description>Revert &quot;[CodeGen] [WinException] Only produce handler data at the end of the function if needed&quot;This caused an explosion in ICF times during linking on Windows when libfuzzerinstrumentation is enabled. For a small binary we see ICF time go from ~0 to~10 s. For a large binary it goes from ~1 s to forevert (I gave up after 30minutes).See comment on the code review.&gt; If we are going to write handler data (that is written as variable&gt; length data following after the unwind info in .xdata), we need to&gt; emit the handler data immediately, but for cases where no such&gt; info is going to be written, skip emitting it right away. (Unwind&gt; info for all remaining functions that hasn&apos;t gotten it emitted&gt; directly is emitted at the end.)&gt;&gt; This does slightly change the ordering of sections (triggering a&gt; bunch of updates to DebugInfo/COFF tests), but the change should be&gt; benign.&gt;&gt; This also matches GCC&apos;s assembly output, which doesn&apos;t output&gt; .seh_handlerdata unless it actually is needed.&gt;&gt; For ARM64, the unwind info can be packed into the runtime function&gt; entry itself (leaving no data in the .xdata section at all), but&gt; that can only be done if there&apos;s no follow-on data in the .xdata&gt; section. If emission of the unwind info is triggered via&gt; EmitWinEHHandlerData (or the .seh_handlerdata directive), which&gt; implicitly switches to the .xdata section, there&apos;s a chance of the&gt; caller wanting to pass further data there, so the packed format&gt; can&apos;t be used in that case.&gt;&gt; Differential Revision: https://reviews.llvm.org/D87448This reverts commit 36c64af9d7f97414d48681b74352c9684077259b.

            List of files:
            /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-recursive-struct.ll</description>
        <pubDate>Tue, 03 Nov 2020 12:01:55 +0000</pubDate>
        <dc:creator>Hans Wennborg &lt;hans@chromium.org&gt;</dc:creator>
    </item>
<item>
        <title>36c64af9 - [CodeGen] [WinException] Only produce handler data at the end of the function if needed</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-recursive-struct.ll#36c64af9</link>
        <description>[CodeGen] [WinException] Only produce handler data at the end of the function if neededIf we are going to write handler data (that is written as variablelength data following after the unwind info in .xdata), we need toemit the handler data immediately, but for cases where no suchinfo is going to be written, skip emitting it right away. (Unwindinfo for all remaining functions that hasn&apos;t gotten it emitteddirectly is emitted at the end.)This does slightly change the ordering of sections (triggering abunch of updates to DebugInfo/COFF tests), but the change should bebenign.This also matches GCC&apos;s assembly output, which doesn&apos;t output.seh_handlerdata unless it actually is needed.For ARM64, the unwind info can be packed into the runtime functionentry itself (leaving no data in the .xdata section at all), butthat can only be done if there&apos;s no follow-on data in the .xdatasection. If emission of the unwind info is triggered viaEmitWinEHHandlerData (or the .seh_handlerdata directive), whichimplicitly switches to the .xdata section, there&apos;s a chance of thecaller wanting to pass further data there, so the packed formatcan&apos;t be used in that case.Differential Revision: https://reviews.llvm.org/D87448

            List of files:
            /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-recursive-struct.ll</description>
        <pubDate>Thu, 10 Sep 2020 10:33:00 +0000</pubDate>
        <dc:creator>Martin Storsj&#246; &lt;martin@martin.st&gt;</dc:creator>
    </item>
<item>
        <title>a36ddf0a - Migrate function attribute &quot;no-frame-pointer-elim&quot;=&quot;false&quot; to &quot;frame-pointer&quot;=&quot;none&quot; as cleanups after D56351</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-recursive-struct.ll#a36ddf0a</link>
        <description>Migrate function attribute &quot;no-frame-pointer-elim&quot;=&quot;false&quot; to &quot;frame-pointer&quot;=&quot;none&quot; as cleanups after D56351

            List of files:
            /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-recursive-struct.ll</description>
        <pubDate>Wed, 25 Dec 2019 00:11:33 +0000</pubDate>
        <dc:creator>Fangrui Song &lt;maskray@google.com&gt;</dc:creator>
    </item>
<item>
        <title>faed8516 - Changing CodeView debug info type record representation in assembly files to make it more human-readable &amp; editable &amp; fixing bug introduced in r364987</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-recursive-struct.ll#faed8516</link>
        <description>Changing CodeView debug info type record representation in assembly files to make it more human-readable &amp; editable &amp; fixing bug introduced in r364987llvm-svn: 365417

            List of files:
            /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-recursive-struct.ll</description>
        <pubDate>Tue, 09 Jul 2019 01:11:02 +0000</pubDate>
        <dc:creator>Nilanjana Basu &lt;nilanjana.basu87@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>c0b55774 - Revert Changing CodeView debug info type record representation in assembly files to make it more human-readable &amp; editable</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-recursive-struct.ll#c0b55774</link>
        <description>Revert Changing CodeView debug info type record representation in assembly files to make it more human-readable &amp; editableThis reverts r364982 (git commit 2082bf28ebea76cc187b508f801122866420d9ff)llvm-svn: 364987

            List of files:
            /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-recursive-struct.ll</description>
        <pubDate>Wed, 03 Jul 2019 00:51:49 +0000</pubDate>
        <dc:creator>Nilanjana Basu &lt;nilanjana.basu87@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>2082bf28 - Changing CodeView debug info type record representation in assembly files to make it more human-readable &amp; editable</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-recursive-struct.ll#2082bf28</link>
        <description>Changing CodeView debug info type record representation in assembly files to make it more human-readable &amp; editablellvm-svn: 364982

            List of files:
            /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-recursive-struct.ll</description>
        <pubDate>Wed, 03 Jul 2019 00:26:23 +0000</pubDate>
        <dc:creator>Nilanjana Basu &lt;nilanjana.basu87@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>e29e30b1 - [llvm-readobj] Change -long-option to --long-option in tests. NFC</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-recursive-struct.ll#e29e30b1</link>
        <description>[llvm-readobj] Change -long-option to --long-option in tests. NFCWe use both -long-option and --long-option in tests. Switch to --long-option for consistency.In the &quot;llvm-readelf&quot; mode, -long-option is discouraged as it conflicts with grouped short options and it is not accepted by GNU readelf.While updating the tests, change llvm-readobj -s to llvm-readobj -S to reduce confusion (&quot;s&quot; is --section-headers in llvm-readobj but --symbols in llvm-readelf).llvm-svn: 359649

            List of files:
            /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-recursive-struct.ll</description>
        <pubDate>Wed, 01 May 2019 05:27:20 +0000</pubDate>
        <dc:creator>Fangrui Song &lt;maskray@google.com&gt;</dc:creator>
    </item>
<item>
        <title>b35e1d7d - [CodeView] Don&apos;t print PointerAttributes when dumping.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-recursive-struct.ll#b35e1d7d</link>
        <description>[CodeView] Don&apos;t print PointerAttributes when dumping.PointerAttributes is a bitwise-or of several other fields, each ofwhich is already printed on its own line with a better explanation.So this doesn&apos;t really help much.llvm-svn: 347275

            List of files:
            /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-recursive-struct.ll</description>
        <pubDate>Tue, 20 Nov 2018 00:10:27 +0000</pubDate>
        <dc:creator>Zachary Turner &lt;zturner@google.com&gt;</dc:creator>
    </item>
<item>
        <title>2c864551 - [DebugInfo] Add DILabel metadata and intrinsic llvm.dbg.label.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-recursive-struct.ll#2c864551</link>
        <description>[DebugInfo] Add DILabel metadata and intrinsic llvm.dbg.label.In order to set breakpoints on labels and list source code aroundlabels, we need collect debug information for labels, i.e., labelname, the function label belong, line number in the file, and theaddress label located. In order to keep these information in LLVMIR and to allow backend to generate debug information correctly.We create a new kind of metadata for labels, DILabel. The formatof DILabel is!DILabel(scope: !1, name: &quot;foo&quot;, file: !2, line: 3)We hope to keep debug information as much as possible even thecode is optimized. So, we create a new kind of intrinsic for labelmetadata to avoid the metadata is eliminated with basic block.The intrinsic will keep existing if we keep it from optimized out.The format of the intrinsic isllvm.dbg.label(metadata !1)It has only one argument, that is the DILabel metadata. Theintrinsic will follow the label immediately. Backend could get thelabel metadata through the intrinsic&apos;s parameter.We also create DIBuilder API for labels to be used by Frontend.Frontend could use createLabel() to allocate DILabel objects, and useinsertLabel() to insert llvm.dbg.label intrinsic in LLVM IR.Differential Revision: https://reviews.llvm.org/D45024Patch by Hsiangkai Wang.llvm-svn: 331841

            List of files:
            /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-recursive-struct.ll</description>
        <pubDate>Wed, 09 May 2018 02:40:45 +0000</pubDate>
        <dc:creator>Shiva Chen &lt;shiva0217@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>9a519a09 - [codeview] Write LF_UDT_SRC_LINE records (PR28251)</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-recursive-struct.ll#9a519a09</link>
        <description>[codeview] Write LF_UDT_SRC_LINE records (PR28251)Differential Revision: http://reviews.llvm.org/D21621llvm-svn: 273495

            List of files:
            /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-recursive-struct.ll</description>
        <pubDate>Wed, 22 Jun 2016 21:22:13 +0000</pubDate>
        <dc:creator>Hans Wennborg &lt;hans@hanshq.net&gt;</dc:creator>
    </item>
<item>
        <title>5b335b86 - [codeview] Add support for splitting field list records over 64KB</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-recursive-struct.ll#5b335b86</link>
        <description>[codeview] Add support for splitting field list records over 64KBThe basic structure is that once a list record goes over 64K, the lastsubrecord of the list is an LF_INDEX record that refers to the nextrecord. Because the type record graph must be toplogically sorted, thismeans we have to emit them in reverse order. We build the type record inorder of declaration, so this means that if we don&apos;t want extra copies,we need to detect when we were about to split a record, and leave spacefor a continuation subrecord that will point to the eventual splittop-level record.Also adds dumping support for these records.Next we should make sure that large method overload lists work properly.llvm-svn: 273294

            List of files:
            /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-recursive-struct.ll</description>
        <pubDate>Tue, 21 Jun 2016 18:33:01 +0000</pubDate>
        <dc:creator>Reid Kleckner &lt;rnk@google.com&gt;</dc:creator>
    </item>
<item>
        <title>a8d57407 - [codeview] Add basic record type translation</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-recursive-struct.ll#a8d57407</link>
        <description>[codeview] Add basic record type translationThis only translates data members for now. Translating overloadedmethods is complicated, so I stopped short of doing that.Reviewers: aaboudDifferential Revision: http://reviews.llvm.org/D20924llvm-svn: 271680

            List of files:
            /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-recursive-struct.ll</description>
        <pubDate>Fri, 03 Jun 2016 15:58:20 +0000</pubDate>
        <dc:creator>Reid Kleckner &lt;rnk@google.com&gt;</dc:creator>
    </item>
</channel>
</rss>
