<?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 bitfields.ll</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><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/bitfields.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/bitfields.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>b60532f8 - [CodeView] Omit forward references for unnamed structs and unions</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/bitfields.ll#b60532f8</link>
        <description>[CodeView] Omit forward references for unnamed structs and unionsCodeview references to unnamed structs and unions are expected to refer to thecomplete type definition instead of a forward reference so Visual Studio canresolve the type properly.Differential Revision: https://reviews.llvm.org/D32498llvm-svn: 334382

            List of files:
            /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/bitfields.ll</description>
        <pubDate>Mon, 11 Jun 2018 01:39:34 +0000</pubDate>
        <dc:creator>Brock Wyma &lt;brock.wyma@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>f52e1922 - Revert r327397 [CodeView] Omit forward references for unnamed structs and ...</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/bitfields.ll#f52e1922</link>
        <description>Revert r327397 [CodeView] Omit forward references for unnamed structs and ...This reverts commit r327397 to investigate a buildbot failure.llvm-svn: 327414

            List of files:
            /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/bitfields.ll</description>
        <pubDate>Tue, 13 Mar 2018 15:56:20 +0000</pubDate>
        <dc:creator>Brock Wyma &lt;brock.wyma@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>4fb91845 - [CodeView] Omit forward references for unnamed structs and unions</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/bitfields.ll#4fb91845</link>
        <description>[CodeView] Omit forward references for unnamed structs and unionsCodeview references to unnamed structs and unions are expected to refer to thecomplete type definition instead of a forward reference so Visual Studio canresolve the type properly.Differential Revision: https://reviews.llvm.org/D32498llvm-svn: 327397

            List of files:
            /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/bitfields.ll</description>
        <pubDate>Tue, 13 Mar 2018 14:14:16 +0000</pubDate>
        <dc:creator>Brock Wyma &lt;brock.wyma@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>05782218 - Canonicalize the representation of empty an expression in DIGlobalVariableExpression</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/bitfields.ll#05782218</link>
        <description>Canonicalize the representation of empty an expression in DIGlobalVariableExpressionThis change simplifies code that has to deal withDIGlobalVariableExpression and mirrors how we treat DIExpressions indebug info intrinsics. Before this change there were two ways ofrepresenting empty expressions on globals, a nullptr and an empty!DIExpression().If someone needs to upgrade out-of-tree testcases:  perl -pi -e &apos;s/(!DIGlobalVariableExpression\(var: ![0-9]*)\)/\1, expr: !DIExpression())/g&apos; &lt;MYTEST.ll&gt;will catch 95%.llvm-svn: 312144

            List of files:
            /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/bitfields.ll</description>
        <pubDate>Wed, 30 Aug 2017 18:06:51 +0000</pubDate>
        <dc:creator>Adrian Prantl &lt;aprantl@apple.com&gt;</dc:creator>
    </item>
<item>
        <title>1eadba1c - Renumber testcase metadata nodes after r290153.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/bitfields.ll#1eadba1c</link>
        <description>Renumber testcase metadata nodes after r290153.This patch renumbers the metadata nodes in debug info testcases afterhttps://reviews.llvm.org/D26769. This is a separate patch because itcauses so much churn. This was implemented with a python script thatpipes the testcases through llvm-as - | llvm-dis - and then goesthrough the original and new output side-by side to insert allcomments at a close-enough location.Differential Revision: https://reviews.llvm.org/D27765llvm-svn: 290292

            List of files:
            /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/bitfields.ll</description>
        <pubDate>Thu, 22 Dec 2016 00:45:21 +0000</pubDate>
        <dc:creator>Adrian Prantl &lt;aprantl@apple.com&gt;</dc:creator>
    </item>
<item>
        <title>bceaaa96 - [IR] Remove the DIExpression field from DIGlobalVariable.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/bitfields.ll#bceaaa96</link>
        <description>[IR] Remove the DIExpression field from DIGlobalVariable.This patch implements PR31013 by introducing aDIGlobalVariableExpression that holds a pair of DIGlobalVariable andDIExpression.Currently, DIGlobalVariables holds a DIExpression. This is not thebest way to model this:(1) The DIGlobalVariable should describe the source level variable,    not how to get to its location.(2) It makes it unsafe/hard to update the expressions when we call    replaceExpression on the DIGLobalVariable.(3) It makes it impossible to represent a global variable that is in    more than one location (e.g., a variable with multiple    DW_OP_LLVM_fragment-s).  We also moved away from attaching the    DIExpression to DILocalVariable for the same reasons.This reapplies r289902 with additional testcase upgrades and a changeto the Bitcode record for DIGlobalVariable, that makes upgrading theold format unambiguous also for variables without DIExpressions.&lt;rdar://problem/29250149&gt;https://llvm.org/bugs/show_bug.cgi?id=31013Differential Revision: https://reviews.llvm.org/D26769llvm-svn: 290153

            List of files:
            /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/bitfields.ll</description>
        <pubDate>Tue, 20 Dec 2016 02:09:43 +0000</pubDate>
        <dc:creator>Adrian Prantl &lt;aprantl@apple.com&gt;</dc:creator>
    </item>
<item>
        <title>73ec0656 - Revert &quot;[IR] Remove the DIExpression field from DIGlobalVariable.&quot;</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/bitfields.ll#73ec0656</link>
        <description>Revert &quot;[IR] Remove the DIExpression field from DIGlobalVariable.&quot;This reverts commit 289920 (again).I forgot to implement a Bitcode upgrade for the case where a DIGlobalVariablehas not DIExpression. Unfortunately it is not possible to safely upgradethese variables without adding a flag to the bitcode record indicating whichversion they are.My plan of record is to roll the planned follow-up patch that adds aunit: field to DIGlobalVariable into this patch before recomitting.This way we only need one Bitcode upgrade for both changes (with aversion flag in the bitcode record to safely distinguish the recordformats).Sorry for the churn!llvm-svn: 289982

            List of files:
            /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/bitfields.ll</description>
        <pubDate>Fri, 16 Dec 2016 19:39:01 +0000</pubDate>
        <dc:creator>Adrian Prantl &lt;aprantl@apple.com&gt;</dc:creator>
    </item>
<item>
        <title>74a835cd - [IR] Remove the DIExpression field from DIGlobalVariable.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/bitfields.ll#74a835cd</link>
        <description>[IR] Remove the DIExpression field from DIGlobalVariable.This patch implements PR31013 by introducing aDIGlobalVariableExpression that holds a pair of DIGlobalVariable andDIExpression.Currently, DIGlobalVariables holds a DIExpression. This is not thebest way to model this:(1) The DIGlobalVariable should describe the source level variable,    not how to get to its location.(2) It makes it unsafe/hard to update the expressions when we call    replaceExpression on the DIGLobalVariable.(3) It makes it impossible to represent a global variable that is in    more than one location (e.g., a variable with multiple    DW_OP_LLVM_fragment-s).  We also moved away from attaching the    DIExpression to DILocalVariable for the same reasons.This reapplies r289902 with additional testcase upgrades.&lt;rdar://problem/29250149&gt;https://llvm.org/bugs/show_bug.cgi?id=31013Differential Revision: https://reviews.llvm.org/D26769llvm-svn: 289920

            List of files:
            /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/bitfields.ll</description>
        <pubDate>Fri, 16 Dec 2016 04:25:54 +0000</pubDate>
        <dc:creator>Adrian Prantl &lt;aprantl@apple.com&gt;</dc:creator>
    </item>
<item>
        <title>03c6d31a - Revert &quot;[IR] Remove the DIExpression field from DIGlobalVariable.&quot;</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/bitfields.ll#03c6d31a</link>
        <description>Revert &quot;[IR] Remove the DIExpression field from DIGlobalVariable.&quot;This reverts commit 289902 while investigating bot berakage.llvm-svn: 289906

            List of files:
            /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/bitfields.ll</description>
        <pubDate>Fri, 16 Dec 2016 01:00:30 +0000</pubDate>
        <dc:creator>Adrian Prantl &lt;aprantl@apple.com&gt;</dc:creator>
    </item>
<item>
        <title>ce139357 - [IR] Remove the DIExpression field from DIGlobalVariable.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/bitfields.ll#ce139357</link>
        <description>[IR] Remove the DIExpression field from DIGlobalVariable.This patch implements PR31013 by introducing aDIGlobalVariableExpression that holds a pair of DIGlobalVariable andDIExpression.Currently, DIGlobalVariables holds a DIExpression. This is not thebest way to model this:(1) The DIGlobalVariable should describe the source level variable,    not how to get to its location.(2) It makes it unsafe/hard to update the expressions when we call    replaceExpression on the DIGLobalVariable.(3) It makes it impossible to represent a global variable that is in    more than one location (e.g., a variable with multiple    DW_OP_LLVM_fragment-s).  We also moved away from attaching the    DIExpression to DILocalVariable for the same reasons.&lt;rdar://problem/29250149&gt;https://llvm.org/bugs/show_bug.cgi?id=31013Differential Revision: https://reviews.llvm.org/D26769llvm-svn: 289902

            List of files:
            /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/bitfields.ll</description>
        <pubDate>Fri, 16 Dec 2016 00:36:43 +0000</pubDate>
        <dc:creator>Adrian Prantl &lt;aprantl@apple.com&gt;</dc:creator>
    </item>
<item>
        <title>2ede126b - DebugInfo: preparation to implement DW_AT_alignment</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/bitfields.ll#2ede126b</link>
        <description>DebugInfo: preparation to implement DW_AT_alignment - Add alignment attribute to DIVariable family - Modify bitcode format to match new DIVariable representation - Update tests to match these changes (also add bitcode upgrade test) - Expect that frontend passes non-zero align value only when it is not default   (was forcibly aligned by alignas()/_Alignas()/__atribute__(aligned())Differential Revision: https://reviews.llvm.org/D25073llvm-svn: 284678

            List of files:
            /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/bitfields.ll</description>
        <pubDate>Thu, 20 Oct 2016 00:13:12 +0000</pubDate>
        <dc:creator>Victor Leschuk &lt;vleschuk@accesssoftek.com&gt;</dc:creator>
    </item>
<item>
        <title>d4135bbc - DebugInfo: New metadata representation for global variables.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/bitfields.ll#d4135bbc</link>
        <description>DebugInfo: New metadata representation for global variables.This patch reverses the edge from DIGlobalVariable to GlobalVariable.This will allow us to more easily preserve debug info metadata whenmanipulating global variables.Fixes PR30362. A program for upgrading test cases is attached to thatbug.Differential Revision: http://reviews.llvm.org/D20147llvm-svn: 281284

            List of files:
            /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/bitfields.ll</description>
        <pubDate>Tue, 13 Sep 2016 01:12:59 +0000</pubDate>
        <dc:creator>Peter Collingbourne &lt;peter@pcc.me.uk&gt;</dc:creator>
    </item>
<item>
        <title>e092dad7 - [codeview] Set the Nested and Scoped ClassOptions based on the scope chain</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/bitfields.ll#e092dad7</link>
        <description>[codeview] Set the Nested and Scoped ClassOptions based on the scope chainThese are set on both the declaration record and the definition record.llvm-svn: 274410

            List of files:
            /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/bitfields.ll</description>
        <pubDate>Sat, 02 Jul 2016 00:11:07 +0000</pubDate>
        <dc:creator>Reid Kleckner &lt;rnk@google.com&gt;</dc:creator>
    </item>
<item>
        <title>6bdc24e7 - [CodeView] Pretty print anonymous scopes</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/bitfields.ll#6bdc24e7</link>
        <description>[CodeView] Pretty print anonymous scopesA namespace without a name should be written out as `anonymousnamespace&apos; while a tag type without a name should be written out as&lt;unnamed-tag&gt;.llvm-svn: 274399

            List of files:
            /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/bitfields.ll</description>
        <pubDate>Fri, 01 Jul 2016 23:12:45 +0000</pubDate>
        <dc:creator>David Majnemer &lt;david.majnemer@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>9319cbc0 - [CodeView] Implement support for bitfields in LLVM</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/bitfields.ll#9319cbc0</link>
        <description>[CodeView] Implement support for bitfields in LLVMCodeView need to know the offset of the storage allocation for abitfield.  Encode this via the &quot;extraData&quot; field in DIDerivedType andintroduced a new flag, DIFlagBitField, to indicate whether or not amember is a bitfield.This fixes PR28162.Differential Revision: http://reviews.llvm.org/D21782llvm-svn: 274200

            List of files:
            /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/bitfields.ll</description>
        <pubDate>Thu, 30 Jun 2016 03:00:20 +0000</pubDate>
        <dc:creator>David Majnemer &lt;david.majnemer@gmail.com&gt;</dc:creator>
    </item>
</channel>
</rss>
